openshift/sdn

NodeLocal DNS causes "172.30.0.0/16 conflicts with host network: 172.30.0.10/32"

Closed this issue · 4 comments

foosinn commented

We recently had to setup NodeLocal DNS as we ran ran into random resolution issues. Since applying it our resolution issues are fully gone.

After a master node reboot we ran into this error:

I0309 15:16:40.762994       1 master.go:52] Initializing SDN master
F0309 15:16:40.768189       1 network_controller.go:59] Error starting OpenShift Network Controller: service IP: 172.30.0.0/16 conflicts with host network: 172.30.0.10/32

For now we worked around the issue by no scheduling the NodeLocal DNS on the master nodes.

Is there a chance to for openshift/sdn to support NodeLocal DNS?

Thanks!

openshift-bot commented

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

openshift-bot commented

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci commented

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.