Replies: 3 comments 1 reply
-
@Ghazgkull : sorry, not an answer but I have exact same issue with an older highly customised From commit histories, @kakkoyun, @paulfantom, @lilic seem to have been involved at least in part in the v0.6->v0.7 changes. Any chance y'all could give @Ghazgkull and I a steer on this - migration-guide specifically suggests posting here for assistance, but sadly there's been no reply for a month? Any help would be really appreciated by me :-) |
Beta Was this translation helpful? Give feedback.
-
Update : See some useful info from @paulfantom in reply at https://kubernetes.slack.com/archives/CFFDS2Z7F/p1624447458459800 |
Beta Was this translation helpful? Give feedback.
-
See also PR #1235 |
Beta Was this translation helpful? Give feedback.
-
Is there any guidance available that can help me navigate the upgrade process from kube-prometheus 0.4 to 0.7?
For background, I've inherited ownership of a kube-prometheus deployment which is currently on version 0.4. After upgrading Kubernetes (EKS) from 1.19 to 1.20 yesterday, our AlertManager has started firing constant alerts about not being able to find "all other members of the cluster". Looking at the K8s compatibility matrix for kube-prometheus, I see that 1.20 isn't supported in our ancient version so I'm guessing we just need to upgrade. I know next to nothing about kube-prometheus and I haven't found any documentation on upgrading except for the 0.7 to 0.8 upgrade, which looks like a major undertaking.
Beta Was this translation helpful? Give feedback.
All reactions