Space On-Premises Help

FAQ and Troubleshooting

Troubleshooting

Space On-Premises pods don't use the updated configuration (Kubernetes installation)

Symptoms:

After you update the configuration of Space On-Premises pods, the pods continue using previous configuration.

Possible cause:

The environment variable files used to configure Space are enabled dynamically, which makes it difficult to calculate the checksum of the file using Helm.

Solution:

  1. Get the names of the Space deployment objects:

    kubectl -n ${KUBE_NAMESPACE} get deployments -l app.kubernetes.io/name=space --output=jsonpath={..metadata.name}
  2. Gracefully shutdown all pods related to the objects from step 1:

    for deployment in $(kubectl -n ${KUBE_NAMESPACE} get deployments -l app.kubernetes.io/name=space --output=jsonpath={..metadata.name}); do kubectl -n ${KUBE_NAMESPACE} scale deploy ${deployment} --replicas=0 done
  3. Restart the Space deployment objects:

    for deployment in $(kubectl -n ${KUBE_NAMESPACE} get deployments -l app.kubernetes.io/name=space --output=jsonpath={..metadata.name}); do kubectl -n ${KUBE_NAMESPACE} scale deploy ${deployment} --replicas=1 done
Last modified: 12 January 2023