-
Notifications
You must be signed in to change notification settings - Fork 41.5k
Fix validation in kubectl create ingress #101377
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
Conversation
Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
@rikatz: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
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.
Good catch and thank you for adding a test for this 😄 .
This probably needs a release note?
Added the release note, will cherry pick to v1.20 and v1.21 once merged :D |
/test pull-kubernetes-e2e-gce-100-performance |
cmd.Flags().StringArrayVar(&o.Rules, "rule", o.Rules, "Rule in format host/path=service:port[,tls=secretname]. Paths containing the leading character '*' are considered pathType=Prefix. tls argument is optional.") | ||
cmd.Flags().StringVar(&o.DefaultBackend, "default-backend", o.DefaultBackend, "Default service for backend, in format of svcname:port") | ||
cmd.Flags().StringArrayVar(&o.Annotations, "annotation", o.Annotations, "Annotation to insert in the ingress object, in the format annotation=value") | ||
cmd.Flags().StringArrayVar(&o.Annotations, "annotation", o.Annotations, "Annotation to insert in the ingress object, in the format annotation=[value]") |
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.
Nit: Are the square brackets to denote that technically the value can be empty/omitted? I feel like that use case might be rare enough for the brackets to cause more confusion than clarification.
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.
fixed, thank you!!
Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
/label tide/merge-method-squash |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eddiezane, rikatz 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 |
/test pull-kubernetes-e2e-kind |
…gress (#101428) * Fix validation in kubectl create ingress Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]> * Fix validation in kubectl create ingress Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
…gress (#101426) * Fix validation in kubectl create ingress Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]> * Fix validation in kubectl create ingress Signed-off-by: Ricardo Pchevuzinske Katz <[email protected]>
Signed-off-by: Ricardo Pchevuzinske Katz [email protected]
What type of PR is this?
/kind bug
What this PR does / why we need it:
When running
kubectl create ingress name --annotation=key
without '=value' it panics due to lack of validationWhich issue(s) this PR fixes:
Fixes kubernetes/kubectl#1041
This was added in PR #94327
/sig cli
/priority important-soon