helm icon indicating copy to clipboard operation
helm copied to clipboard

Why did I specify clusterIP for CoreDNS?

Open rabbagliettiandrea opened this issue 9 months ago • 0 comments

Hi everyone,

I was reviewing the foundation configurations of one of our production clusters, and I noticed something in the values.yaml for CoreDNS. Specifically, I saw that I had manually set the clusterIP like this:

replicaCount: 2  
service:  
  clusterIP: "10.100.0.10"  

The issue I'm running into now is that I'm unable to upgrade CoreDNS because it says the IP is already bound.

The problem is... I honestly can't remember why I set the clusterIP in the first place.

Does anyone have any ideas? Could this have something to do with not using KubeDNS? I'm a bit confused.

Here's my kubectl get all -n kube-system:

Image

rabbagliettiandrea avatar Feb 24 '25 17:02 rabbagliettiandrea