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

helm: Use a more explicit value for ingress for K8s 1.18 #9280

Merged
merged 1 commit into from Dec 2, 2021

Conversation

TomHellier
Copy link
Contributor

Description of your changes:
Updating minor versions of kubernetes test environments, and running helm charts against all supported environments.

Which issue is resolved by this Pull Request:
Resolves #9174

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
  • Skip Tests for Docs: Add the flag for skipping the build if this is only a documentation change. See here for the flag.
  • Skip Unrelated Tests: Add a flag to run tests for a specific storage provider. See test options.
  • Reviewed the developer guide on Submitting a Pull Request
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.
  • Pending release notes updated with breaking and/or notable changes, if necessary.
  • Upgrade from previous release is tested and upgrade user guide is updated, if necessary.
  • Code generation (make codegen) has been run to update object specifications, if necessary.

@TomHellier TomHellier changed the title wip: Test helm charts on multiple versions & attempt to fix bug Test helm charts on multiple versions & attempt to fix bug Dec 1, 2021
@TomHellier TomHellier marked this pull request as ready for review December 1, 2021 11:11
@travisn
Copy link
Member

travisn commented Dec 1, 2021

@TomHellier Thanks for the fix and verifying on all the K8s versions! How about if you revert the commit that tests on more k8s versions, then we can get this merged.

The networking.k8s.io/v1 api defines the backend differently
to networking.k8s.io/v1beta1 and extensions/v1beta1

Signed-off-by: Tom Hellier <me@tomhellier.com>
Copy link
Member

@travisn travisn left a comment

Choose a reason for hiding this comment

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

LGTM. Could you also open a PR for this directly to the release-1.7 branch? The bot will have a merge conflict with the backport since the cluster/charts was renamed to deploy/charts in master.

@travisn
Copy link
Member

travisn commented Dec 1, 2021

LGTM. Could you also open a PR for this directly to the release-1.7 branch? The bot will have a merge conflict with the backport since the cluster/charts was renamed to deploy/charts in master.

Already done I see with #9293. :)

@travisn travisn changed the title Test helm charts on multiple versions & attempt to fix bug helm: Use a more explicit value for ingress for K8s 1.18 Dec 2, 2021
travisn added a commit that referenced this pull request Dec 2, 2021
helm: Use a more explicit value for ingress (backport #9280)
@travisn travisn merged commit 2efa571 into rook:master Dec 2, 2021
mergify bot added a commit that referenced this pull request Dec 2, 2021
helm: Use a more explicit value for ingress for K8s 1.18 (backport #9280)
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.

rook cluster helm chart no longer deploys an ingress on k8s 1.17
3 participants