Skip to main content

Okteto Enterprise Troubleshooting Guide

UPGRADE FAILED: “$name” has no deployed releases#

This error will occur on your second install/upgrade if your initial install failed. If the first instal failed, delete the existing install before trying again:

helm uninstall <release-name>

Registry or Buildkit pods keep restarting#

This can happen when the pods can't read/write from your cloud storage bucket. Double check that the cloud IAM you created has read/write access to the specified bucket.

Another reason this might happen is if the SSL certificate is not valid. You can check its status by running:

kubectl get certificate -l=app.kubernetes.io/part-of=okteto -n=okteto

Invalid Certificate#

Okteto Enterprise uses Let's Encrypt to generate the wildcard certificate. If the certificate is not valid, check the following:

  • The cloud provider credentials you are using have read/write access to the subdomain you selected
  • The subdomain can be resolved from the internet

The logs of the cert-manager pod might also contain information on the problem. You can get the logs by by running:

kubectl logs -f -l=app.kubernetes.io/name=cert-manager --namespace=okteto

Deployment pipelines stay in "progressing" forever#

This can happen for several reasons, among others, the installer job couldn't be started due to an error in Kubernetes API, or due to an overload in the cluster. In order to find out what the problem is, there's a way to list all the jobs and pods for a specific pipeline.

You need the pipeline name (it is the name displayed on Okteto UI) and the namespace where it is deployed. With that information, you can get jobs and pods running these commands:

kubectl get jobs -l=dev.okteto.com/pipeline-name=movies -l=dev.okteto.com/pipeline-namespace=cindylopez --namespace=okteto
kubectl get pods -l=dev.okteto.com/pipeline-name=movies -l=dev.okteto.com/pipeline-namespace=cindylopez --namespace=okteto

We are here to help#

Reach out to us, we're always happy to help!