Skip to content
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

Merged
merged 2 commits into from
Jan 4, 2022
Merged

Update ingress api version, extension/v1beta1 will not be supported i… #183

merged 2 commits into from
Jan 4, 2022

Conversation

wangshu3000
Copy link
Contributor

…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:

  1. dashboard-ingress
  2. grafana-ingress
  3. proxy-ingress
  4. pulsar-manager-ingress

Verifying this change

  • Make sure that the change passes the CI checks.

…n new k8s version, this change keep backward compatibility for lower kubernetes version
@wangshu3000
Copy link
Contributor Author

Could anybody in the team please review this PR? Thanks.

Copy link
Member

@lhotari lhotari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work!

Copy link
Member

@michaeljmarshall michaeljmarshall left a 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.

charts/pulsar/templates/dashboard-ingress.yaml Outdated Show resolved Hide resolved
@michaeljmarshall
Copy link
Member

@lhotari - do you know why the CI checks wouldn't have run for this PR? I haven't seen that happen before.

Copy link
Member

@michaeljmarshall michaeljmarshall left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ingresses still use the extensions/v1beta1 versioned resource
3 participants