Kubernetes: Pod stuck at Init:0/1

The Java application pod doesn't finish the instrumentation init container step.

After you activate Secure Application Java instrumentation in Kubernetes, the application pod stays in Init:0/1.

Kubernetes can't pull the Java instrumentation init container image. For example, the image tag might be incorrect, or the image might not be available from the configured registry.

  1. Run kubectl describe pod for the affected pod and check the event output for image pull errors.
  2. Verify the secureAppCsaImage Helm value, if you set it.
  3. If you don't need a custom image, remove the custom image value and let the Splunk OpenTelemetry Collector Helm chart manage the Java instrumentation image.