-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
fix typo and duplicated declaration of ingressclasses #8591
fix typo and duplicated declaration of ingressclasses #8591
Conversation
Hi @spaced. 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. |
@@ -16,15 +16,16 @@ rules: | |||
- apiGroups: [""] | |||
resources: ["services"] | |||
verbs: ["get", "list", "watch"] | |||
- apiGroups: ["extensions","networking.k8s.io"] |
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.
I expect this was in place for some beta API compatibility. Did you check the impact of removing the extensions
apiGroup?
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.
The stable API(networking.k8s.io) of ingress has been added since v1.19, and the beta API of ingress has been removed since Kubernetes v1.22 as https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122
On Kubespray, kube_version_min_required is v1.21.0.
So I think it is fine to remove this extensions
.
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.
Thanks @oomichi for the clarification!
verbs: ["get", "list", "watch"] | ||
- apiGroups: [""] | ||
resources: ["events"] | ||
verbs: ["create", "patch"] | ||
- apiGroups: ["extensions","networking.k8s.io"] | ||
resources: ["ingresses/status"] | ||
verbs: ["update"] | ||
- apiGroups: [networking.k8s.io"] | ||
- apiGroups: ["networking.k8s.io"] |
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.
The list of verbs and apiGroups is the same as the one above. It looks cleaner to just group resources in the entry above and delete this typo'ed line.
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.
That is a nice point.
I agree with @cristicalin here
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.
@cristicalin @oomichi
nope, i do not agree: the one above is only for ingress/status
and update.
I recommend to not reinvent the wheel and stay close to https://github.com/kubernetes/ingress-nginx/blob/main/deploy/static/provider/baremetal/1.21/deploy.yaml#L209 for easier merge in the future.
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.
Thank you for your explanation, that makes sense for easy maintenance.
/ok-to-test
/lgtm
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.
/cc @oomichi
@@ -16,15 +16,16 @@ rules: | |||
- apiGroups: [""] | |||
resources: ["services"] | |||
verbs: ["get", "list", "watch"] | |||
- apiGroups: ["extensions","networking.k8s.io"] |
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.
The stable API(networking.k8s.io) of ingress has been added since v1.19, and the beta API of ingress has been removed since Kubernetes v1.22 as https://kubernetes.io/docs/reference/using-api/deprecation-guide/#ingress-v122
On Kubespray, kube_version_min_required is v1.21.0.
So I think it is fine to remove this extensions
.
verbs: ["get", "list", "watch"] | ||
- apiGroups: [""] | ||
resources: ["events"] | ||
verbs: ["create", "patch"] | ||
- apiGroups: ["extensions","networking.k8s.io"] | ||
resources: ["ingresses/status"] | ||
verbs: ["update"] | ||
- apiGroups: [networking.k8s.io"] | ||
- apiGroups: ["networking.k8s.io"] |
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.
That is a nice point.
I agree with @cristicalin here
ping @spaced Could you please address the comments above so we can merge this contribution? |
i already commented, we should not
this is not the same: it has I recommend to stay close what upstream provides: https://github.com/kubernetes/ingress-nginx/blob/main/deploy/static/provider/baremetal/1.21/deploy.yaml#L209 for easier merge in the future. |
Sorry, I missed your comment @spaced , thanks for the explanation. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin, spaced 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: