-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
External load balancer task uses assigned IPv4 address #14665
Comments
/language zh |
/language en |
/remove-language zh |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Fixed via #14677 |
@sftim: Closing this issue. In response to this:
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. |
This is a Bug Report
Problem: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/ uses a real, assigned IPv4 address:
123.45.67.89
Proposed Solution:
Use a documentation IP address instead; that is, one that's inside
192.0.2.0/24
Page to Update:
https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/
child of issue #14664
The text was updated successfully, but these errors were encountered: