79836294

Date: 2025-12-02 20:23:23
Score: 2.5
Natty:
Report link

As others commented, the way this chart works is too generic and might not be the best idea to allow any initContainer from the values.

That being said, the error you are having might be due to the new deployment not working and so the POD not getting really replace, which would explain why you still see the initContainer. Can you confirm that when you deploy the hel mchart without any init container it does replace the latest deployment and POD? you can see the kubectl events to verify there isn't any error and also describe the deployment.

kubectl get events --sort-by=.metadata.creationTimestamp

Replace <deployment_name> below:

kubectl describe deployment <deployment_name>

Also confirm that the initContaienr you see is not coming from other configurations (for example some tools as Istio inject initContainers to every POD)

If this doesn't work please share the values.yaml and the deployment describe yaml.

Reasons:
  • RegEx Blacklisted phrase (2.5): please share
  • Long answer (-0.5):
  • Has code block (-0.5):
  • Contains question mark (0.5):
  • Low reputation (0.5):
Posted by: Mauro