-
Notifications
You must be signed in to change notification settings - Fork 220
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
Update ingress api version, extension/v1beta1 will not be supported i… #183
Update ingress api version, extension/v1beta1 will not be supported i… #183
Conversation
…n new k8s version, this change keep backward compatibility for lower kubernetes version
Could anybody in the team please review this PR? Thanks. |
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 work!
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.
Great work @wangshu3000! I think it might make sense to modify the conditionals in the PR. Let me know what you think. Otherwise, this looks good to me.
@lhotari - do you know why the CI checks wouldn't have run for this PR? I haven't seen that happen before. |
…ities.KubeVersion.Version
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.
LGTM. @wangshu3000 - looks like the tests ran against this latest PR, so that's good too.
…n new k8s version, this change keep backward compatibility for lower kubernetes version
Fixes #157
Motivation
The ingress api extensions/v1beta1 version will not be supported in k8s version 1.22+, need to update to new networking.k8s.io/v1.
This PR also keep support for old k8s version, to provide enough compatibility.
Modifications
Updated the api version for below 4 components:
Verifying this change