-
Notifications
You must be signed in to change notification settings - Fork 40k
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
kubectl describe more fields for ingress #17425
Conversation
Labelling this PR as size/M |
GCE e2e build/test failed for commit b6c4f74a1108dad2345c4abdf109ed155a204a05. |
b6c4f74
to
557155a
Compare
GCE e2e test build/test passed for commit 557155a91d47acac70f8dbf2861e84dbfc7c94ac. |
@feiskyer thanks! this looks good. Can you give me some example output? |
@bprashanth A simple demo is # ./kubectl describe ingress
Name: test-ingress
Namespace: default
Labels: <none>
Rules:
Backend: nginx:8078
Endpoints: 192.168.123.10:80,192.168.123.11:80
Annotations:
No events. |
LGTM, sorry for delay |
@k8s-bot test this Tests are more than 48 hours old. Re-running tests. |
GCE e2e build/test failed for commit 557155a91d47acac70f8dbf2861e84dbfc7c94ac. |
557155a
to
7fc206b
Compare
Thanks @bprashanth, I rebased this to trigger e2e tests. |
GCE e2e build/test failed for commit 7fc206b9bc3346de3d6f1857dc7d6d0a4cabbbbf. |
PR changed after LGTM, removing LGTM. |
7fc206b
to
0d61141
Compare
GCE e2e build/test failed for commit 0d61141. |
@bprashanth Could you help to check why GCE e2e test failing? |
@k8s-bot e2e test this |
GCE e2e test build/test passed for commit 0d61141. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e test build/test passed for commit 0d61141. |
Automatic merge from submit-queue |
Auto commit by PR queue bot
kubectl describe more fields (including endpoints) for ingress
Ref #16927 CC @janetkuo