How to debug a failing CatalogSource
The Catalog operator will constantly update the
CatalogSources to reflect its current state. You can check the
Status of your
CatalogSource with the following command:
$ kubectl -n my-namespace get catsrc my-catalog -o yaml | yq r - status
Note: It is possible that the
Statusis missing, which suggests that the Catalog operator is encountering an issue when processing the
CatalogSourcein a very early stage.
Status block does not provide enough information, check the Catalog operator’s logs.
If you are still unable to identify the cause of the failure, check if a pod was created for the
CatalogSource. If a pod exists, review the pod’s yaml and logs:
$ kubectl -n my-namespace get pods NAME READY STATUS RESTARTS AGE my-catalog-ltdlp 1/1 Running 0 8m31s $ kubectl -n my-namespace get pod my-catalog-ltdlp -o yaml ... $ kubectl -n my-namespace logs my-catalog-ltdlp ...
I’m not sure if a specific version of an operator is available in a CatalogSource
First verify that the
CatalogSource contains the operator that you want to install:
$ kubectl -n my-namespace get packagemanifests NAME CATALOG AGE ... portworx My Catalog Source 14m postgres-operator My Catalog Source 14m postgresql My Catalog Source 14m postgresql-operator-dev4devs-com My Catalog Source 14m prometheus My Catalog Source 14m ...
If the operator is present, check if the version you want is available:
$ kubectl -n my-namespace get packagemanifests my-operator -o yaml
My CatalogSource cannot pull images from a private registry
If you are attempting to pull images from a private registry, make sure to specify a secret key in the