coredns / coredns/helm

Why did I specify clusterIP for CoreDNS?

Open
#201 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Mustache
Stars
146
Forks
145
Avg merge
6d 5h
Merged PRs (30d)
2

Description

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](https://github.com/user-attachments/assets/10fc2978-bde0-4fc3-8e3f-dc0bc3ff2464)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.