-
Notifications
You must be signed in to change notification settings - Fork 486
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
Add READY and ADDRESS to gateway printer columns #743
Add READY and ADDRESS to gateway printer columns #743
Conversation
Hi @howardjohn. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 looks great, thanks @howardjohn! /ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: howardjohn, robscott 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 |
Actually, missed that there were changes to v1a1 CRDs. Although these are not breaking in any way, I think we should generally consider v1alpha1 frozen. /hold |
apis/v1alpha1/gateway_types.go
Outdated
// +kubebuilder:printcolumn:name="Address",type=string,JSONPath=`.status.addresses[*].value` | ||
// +kubebuilder:printcolumn:name="Ready",type=string,JSONPath=`.status.conditions[?(@.type=="Ready")].status` |
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.
Suggest removing from v1alpha1 since we haven't made any other v1alpha1 changes since v0.3.0
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.
done
Joined with kubernetes-sigs/gateway-api#743, this allows displaying non-empty results when there is no external IP for the Gateway (ie its a cluster IP gateway)
/hold cancel |
Joined with kubernetes-sigs/gateway-api#743, this allows displaying non-empty results when there is no external IP for the Gateway (ie its a cluster IP gateway)
Let's optimize for the regular case. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add new columns. This allows at glance finding out how to access the gateway, and if its ready to be accessed
Example:
Ingress for comparison: