Skip to content

Portal Container remains in "ContainerCreating" Status

To check possible root causes, execute the kubectl describe pod portal-0 command.

Unmounted "service-detailconfig" Volume

The service-detailconfig volume is a ConfigMap that contains multiple service details. This ConfigMap is created by the job manager. A typical reason for this is that the job manager is unable to execute the `kubectl' commands.

Validate no_proxy Settings of the Job-Manager StatefulSet

  1. Execute the kubectl edit secret job-manager-secret command to enter the definition file.

  2. The job-manager is mounting the proxy settings as environment variables into the container.

  3. Values are environment variables stored as K8s secrets, hence they might contain confidential data.

  4. Decode the no_proxy value in the echo "<value of no_proxy key>" | base64 -d data field.

  5. Ensure that the K8s service and Pod CIDR ranges are part of the no_proxy variable.