3

I have a Rancher Kubernetes Cluster running and my application containing sevral pods is running as a helm chart. When I wanted to update my application, I updated my container image and redeployed the pod. Since 3 years, this worked well. Suddenly, when I try to redeploy my frontend pod, I get the following error message from the rancher gui:

Deployment generation is 35, but latest observed generation is 34

I googled the error and "deployment generation", but it seems umcommon to have this problem. There are almost no results from google, what makes me wonder...The pod is not getting deployed currently.

Does anyone has a hint on why this suddenly happens and how to fix that?

Thanks in advance,

Ben

2 Answers2

0

Just need to pause and redeploy the deployment. It was due to consecutive failures of the deployment to try to be at a running state due to so internal errors of the app like the database being down or something else which was an internal server error.

-1

I don't know the exact solution to this, but I had to reboot the whole cluster to get rid of this message and regain the ability to deploy. Seems to be something really odd.