Troubleshooting your deployment in Kubernetes environment
This section describes how troubleshoot in Kubernetes environment.
The troubleshooting steps assumes that Kubectl
command line tool is installed
and configured in your environment.
Run the following checks to assist you with troubleshooting process.
Generic Checks
- Get nodes information and check the status of nodes is
Ready
kubectl get nodes -o wide
- Review the Persistent Volume and Persistent Volume Claim information and ensure they match with
your deployment YAML
files
kubectl describe pv <pv name> -n <namespace>
- Get information about the pods after the Secure Proxy containers have been
deployed:
kubectl get pods -n <namespace> -o wide
- Retrieve the logs for a particular
pod
kubectl logs -f <pod name> -n <namespace>
- Get pod
details
kubectl describe pods <pod name> -n <namespace>
Rerun a failed container deployment job
If a Kubernetes deployment fails, you can investigate the cause and then re-run the deployment
from the command line:
- Delete the failed deployment using the below
command
helm uninstall <release-name> -n <namespace>
- Delete the persistent volume
kubectl delete pv <pv-name>
- Re-run the deployment steps described in Deploying IBM Sterling Secure Proxy in a Kubernetes based Container Platform.
View Container Logs
- Check container logs using the
command
kubectl logs -f <pod name> -n <namespace>
- From the mapped path on Storage Volume, check the silent installation logs
APPStartup.log
inside the CM or ENGINE directory.