When the Opstrace cluster or parts of it appear to not be healthy then debugging should start with getting insights about the underlying Kubernetes (k8s) cluster and its deployments.
Make sure use the same
AWS_SECRET_ACCESS_KEY that were used for creating the Opstrace cluster.
aws eks update-kubeconfig --name <clustername> --region <awsregion>
aws eks update-kubeconfig --name testcluster --region us-west-2
When the Opstrace cluster or parts of it appear to not be healthy then debugging should start with getting an overview over all k8s deployments and individual container states. This can be obtained with the following command:
kubectl describe all --all-namespaces > describe_all.out
This will reveal when a certain container is for example in a crash loop, or when it never started in the first place as of for example an error while pulling the corresponding container image.
When the Opstrace controller (a deployment running in the Opstrace cluster) is suspected to have run into a problem then it is important to fetch and inspect its logs:
kubectl logs deployment/opstrace-controller \--all-containers=true --namespace=kube-system > controller.log
It's possible your installation can fail waiting for the certificates to be ready. When this happens, you'll see messages such as the following:
info: waiting for 0 DaemonSetsinfo: waiting for 0 StatefulSetsinfo: waiting for 1 Certificatesdebug: Waiting for Certificate ingress/https-cert to be ready
And when the installation fails:
info: waiting for 0 DaemonSetsinfo: waiting for 0 StatefulSetsinfo: waiting for 1 Certificateswarning: cluster creation attempt timed out after 2400 secondserror: 3 attempt(s) failed. Stop retrying. Exit.
This is a known problem that we are tracking in these issues:
- ci: waiting "for Certificate ingress/https-cert to be ready" didn't resolve
- Certificate sometimes fails to issue properly
If this happens, the recommended workaround is to restart the certificate request process.
First, if the installation process is stuck, you can exit by pressing Ctrl-C. Then proceed to connect kubectl to your Opstrace cluster.
Afterward, find the certificate request created by cert-manager:
$ kubectl -n ingress get certificaterequestNAME READY AGEhttps-cert-XXXXX False 30mkubed-apiserver-cert-XXXXX True 30m
The certificate request starts with
https-cert- followed by five random characters.
Delete the failed certificate request:
kubectl -n ingress delete certificaterequest https-cert-XXXXX
And delete the certificate to have the controller recreate it and restart the request process:
kubectl -n ingress delete certificate http-cert
Check the installation succeeded by reissuing the
./opstrace create aws $OPSTRACE_NAME \-c opstrace-config.yaml
When everything is done, you'll see the following log line:
info: cluster creation finished: $OPSTRACE_NAME (aws)