Troubleshoot HorizontalPodAutoscaler errors if Jama Connect deployment fails
In previous versions of Jama Connect with Kubernetes 1.27.6, the HorizontalPodAutoscaler resources for horizontal scaling were deprecated. If your Jama Connect deployment fails with the following error, you must manually update the Kubernetes secret associated with the deployed Helm release and redeploy Jama Connect.
Important
This process applies only to environments with horizontal scaling enabled.
To modify the Kubernetes Helm release secret:
Retrieve the name of the secret associated with the latest deployed Helm release:
kubectl get secret -l owner=helm,status=deployed,name=application | awk '{print $1}' | grep -v NAME
Use the secret to save the latest deployed release details to a file:
kubectl get secret <secret-name> -o yaml > release.yaml
Create a backup of the file you created:
cp release.yaml release.bak
Decode and generate output of the release object (JSON) found in the file you created:
cat release.yaml | grep -oP '(?<=release: ).*' | base64 -d | base64 -d | gzip -d > release.data.decoded
Using an editor tool, edit the release object data by changing all occurrences that reference the deprecated API version (autoscaling/v2beta1) with the new value (autoscaling/v2) found in the manifest field.
Encode the modified release object:
cat release.data.decoded | gzip | base64 | base64
If the output contains line breaks, you must remove them before you can continue.
Using an editor tool, replace the JSON property value “data.release” in release.yaml with the newly encoded release object value you just created.
Apply the release file:
kubectl apply -f release.yaml
Deploy Jama Connect.