-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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.
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
updating Pod DNS config example to use documentation IP address #39169
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I don't think this is necessary. /hold |
sftim whats your thought about this? |
@@ -10,7 +10,7 @@ spec: | |||
dnsPolicy: "None" | |||
dnsConfig: | |||
nameservers: | |||
- 1.2.3.4 | |||
- 192.0.2.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To address @tengqm's reservation, how about:
- 192.0.2.1 | |
- 192.0.2.1 # this is an example |
or use an AS112 IP address, such as 10.42.0.1?
- 192.0.2.1 | |
- 10.42.0.1 # this is an example |
How about either of those approaches? I notice that the IPv6 example is already using a documentation IP address.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding a comment is good and clear enough.
Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note added, please review
/hold cancel |
LGTM label has been added. Git tree hash: ea55adac65ec3440ca5ea6182c49c8af6770671f
|
@@ -306,7 +306,7 @@ When the Pod above is created, the container `test` gets the following contents | |||
in its `/etc/resolv.conf` file: | |||
|
|||
``` | |||
nameserver 1.2.3.4 | |||
nameserver 192.0.2.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add a comment like # 192.0.2.1 is an example IP
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lines that contain a semicolon (;) or hash character (#) in the first column are treated as comments.
For resolv.conf
, that comment does need to be on a line by itself.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: reylejano The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@reetasingh , |
/retest |
Hi @reylejano pushed an empty commit |
…rnetes#39169) * updating Pod DNS config example to use documentation IP address * add this is an example in note * empty commit
Fix #39166
Problem:
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config uses 1.2.3.4 as the example DNS server. It's better to use an IP address reserved for documentation.
Proposed Solution:
Change the example manifest and web page to use IP address 192.0.2.1 ( from the 192.0.2.0/24 block)