Troubleshooting

If you run into any issues while deploying vCluster Platform, this page contains some information that may help you resolve deployment issues. If you're still stuck, join the Slack #vCluster channel where you can ask questions.

Troubleshoot

Flag --reset

If you need a clean vCluster Platform installation, you can use the --reset flag to tell vCluster CLI to purge any previous vCluster Platform installs:

vCluster platform start --reset    # --insecure  ...add any other `vCluster platform start` flags if needed

Debug ImageErr + ImagePullBackOff

If your vCluster Platform pods are not starting because the vCluster Platform images cannot be pulled, you may need to use a private image registry rather than pulling vCluster Platform images from over the internet.

Use port-forwarding

You can always try to connect to vCluster Platform directly and circumvent any potential networking issues introduced at the load balancer and ingress controller level.

To start port-forwarding, either use vCluster platform start or run:

kubectl port-forward deploy/loft -n vCluster-platform 8080:10443

After that you can access vCluster Platform at https://localhost:8080. You can even login with the vCluster CLI to this URL with:

vCluster platform login localhost:8080 --insecure

If you can access vCluster Platform via port-forwarding only, this is usually an indicator that the problem might be related to a misconfigured LoadBalancer or Ingress Controller.