-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Ingress's address has many repeated ip or hostname #48654
Comments
@FengyunPan There are no sig labels on this issue. Please add a sig label by: |
k8s-github-robot
added
the
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
label
Jul 8, 2017
/sig api |
/sig cli |
k8s-github-robot
removed
the
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
label
Jul 8, 2017
FengyunPan
pushed a commit
to FengyunPan/kubernetes
that referenced
this issue
Jul 29, 2017
k8s-github-robot
pushed a commit
that referenced
this issue
Aug 8, 2017
Automatic merge from submit-queue Filter duplicate ips or hostnames for ingress Fix issue: #48654 **Release note**: ```release-note NONE ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
# kubectl get ingress -o wide
NAME HOSTS ADDRESS PORTS AGE
nginx-ingress www.cluster.local 10.0.0.9,10.0.0.5,10.0.0.8,10.0.0.8,10.0.0.6,10.0.0.6 80, 443 1m
# kubectl describe ing
Name: nginx-ingress
Namespace: default
Address: 10.0.0.9,10.0.0.5,10.0.0.8,10.0.0.8,10.0.0.6,10.0.0.6
Default backend: default-http-backend:80 (10.100.99.12:8080)
What you expected to happen:
ADDRESS just be 10.0.0.5,10.0.0.6,10.0.0.8,10.0.0.9
How to reproduce it (as minimally and precisely as possible):
kubectl get ingress -o wide
kubectl describe ingress
The text was updated successfully, but these errors were encountered: