Troubleshoot SDS in Kubernetes and OpenShift

The pod remains in Pending. Check PVC events and available capacity. Confirm that the StorageClass exists, supports ReadWriteOnce, and can provision volumes in the pod's availability zone. You should also verify CPU and memory scheduling.

  • For Kubernetes:

    Copy 
    kubectl describe pod sds-0 -n <namespace>
    kubectl describe pvc -n <namespace>

  • For OpenShift:

    Copy 
    oc describe pod sds-0 -n <namespace>
    oc describe pvc -n <namespace>

The pod reports ImagePullBackOff. Verify the image repository, tag, and digest, confirm that the image was pushed to the registry, ensure the node network and DNS can reach the registry, and confirm that image.pullSecret references a Secret in the SDS namespace.

The pod is rejected on OpenShift. Ensure that value-openshift.yaml was provided and that the namespace's SCC permits a non-root workload with the required volume access. Inspect pod events using the following command:

Copy 
oc describe pod sds-0 -n <namespace>

Ingress or Route access fails. Confirm DNS resolution, the configured ingress class or OpenShift Route, relevant load balancer and firewall rules, and the TLS certificate. Check the SDS Service endpoints and ingress controller or router logs. Use a port-forward to validate SDS independently of the ingress path.

The pod starts and then restarts. Review container logs and events, check for resource limit or probe failures, and confirm that all persistent volumes are mounted and writable by the non-root container user.