Depending on your installation, you can use Calyptia, Helm, or kubectl's command-line tools to diagnose and resolve issues with your Core Operator and Instance installation.
Troubleshooting Core Operator
If you use Calyptia CLI to install Core Operator and get the following error message, you're probably using an older version of Calyptia CLI:
calyptia:/lib/x86_64-linux-gnu/libc.so.6:version`GLIBC_2.34' not found (required by calyptia)calyptia: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32'notfound (required bycalyptia)
Core Operator operations can only be carried out with Calyptia CLI version 1.4.7 or later. You will need to upgrade Calyptia CLI.
Verifying your Core Operator Installation
You can examine the logs of your Core Operator installation to verify that your installation is successful and to diagnose any issues you may encounter using Calyptia CLI.
A Core instance is a single deployment with two containers that synchronizes pipeline resources between both the Cloud API and the cluster.
to-cloud container pushes every newly created/updated pipeline to Cloud API and ensures that namespaces from the cluster are synchronized with Cloud API.
from-cloud container pulls all pipelines from CloudAPI and pushes them to the cluster as Pipeline Custom Resources.
To get a list of your core instances, use the following command:
calyptiagetcore_instances
You should get a list of your core instances from where you can see your running, failed, and unreachable instances.
The coretesting instance is unreachable, and coreinstance01 is running.
To obtain more details about your core instance, you can view the logs using kubectl logs from each container by specifying your core instance's container name with your pod name.
kubectllogs{CORE_POD_NAME}from-cloud
The logs from a running from-cloud sync container look like this: