Skip to content

explain why we cannot currently use the dnsConfig #921

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
deads2k wants to merge 2 commits into from
Closed

explain why we cannot currently use the dnsConfig #921

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a8ddcb
Update dnsPolicy to allow consistent resolution of the internal LB
deads2k Mar 29, 2023
3fea0b9
explain why we cannot currently use the dnsConfig
deads2k Mar 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion install/0000_00_cluster-version-operator_03_deployment.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,14 @@ spec:
fieldPath: spec.nodeName
- name: CLUSTER_PROFILE
value: {{ .ClusterProfile }}
dnsPolicy: ClusterFirstWithHostNet
# this pod is hostNetwork and uses the internal LB DNS name when possible, which the kubelet also uses.
# this dnsPolicy allows us to use the same dnsConfig as the kubelet, without access to read it ourselves.
dnsPolicy: Default
# The dnsConfig below doesn't work because the IP range for the service network is configurable.
# There is no easy spot to perform this injection, though the CVO could be made to look up and substitute the value.
# dnsConfig:
# nameservers:
# - 172.30.0.10
hostNetwork: true
nodeSelector:
node-role.kubernetes.io/master: ""
Expand Down