-
Notifications
You must be signed in to change notification settings - Fork 7
feat: Deploy snapshot-controller as separate addon #734
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50f485d
to
8fa5cf2
Compare
fd87fd1
to
dc7c1f6
Compare
e5717e3
to
e31bb3b
Compare
dc7c1f6
to
8732705
Compare
e31bb3b
to
a2332de
Compare
8732705
to
0397b48
Compare
a2332de
to
13fdac2
Compare
0397b48
to
fc607fc
Compare
13fdac2
to
ced4eb6
Compare
fc607fc
to
9610953
Compare
supershal
previously approved these changes
Jun 24, 2024
ced4eb6
to
ee8e7af
Compare
8d07c51
to
0267743
Compare
This PR/issue depends on:
|
Currently both Nutanix CSI and AWS EBS CSI handlers deploy the snapshot-controller. Generally the snapshot-controller should be treated as a separate addon that all compatible CSI providers can take advantage of. This commit removes the snapshot-controller from both Nutanix and AWS EBS CSI, and instead deploys the snapshot-controller separately so they can both use it as necessary. Deployment tested manually on AWS via e2e test suite as well as the automated Docker test suite running in CI.
0267743
to
529bcd0
Compare
mhrabovcin
approved these changes
Jun 27, 2024
faiq
approved these changes
Jun 27, 2024
Merged
jimmidyson
added a commit
that referenced
this pull request
Jun 27, 2024
This commit refactors some of the existing HelmAddon code used in various handlers to a common applier, thus reducing code maintenance. There are a number of other places where this could be applied, but they currently have specific behaviour that is harder to generalise and as such I have not refactored those handlers yet. Depends on #734.
jimmidyson
added a commit
that referenced
this pull request
Jun 27, 2024
🤖 I have created a release *beep* *boop* --- ## 0.11.0 (2024-06-27) <!-- Release notes generated using configuration in .github/release.yaml at main --> ## What's Changed ### Exciting New Features 🎉 * feat: Configure namespace sync in helm chart by @dlipovetsky in #726 * feat: Support CRS for local-path provisioner and add CSI e2e by @jimmidyson in #737 * feat: Support HelmAddon strategy for AWS EBS by @jimmidyson in #732 * feat: Deploy snapshot-controller as separate addon by @jimmidyson in #734 * feat: Update AWS CCM versions and add HelmAddon strategy by @jimmidyson in #748 ### Fixes 🔧 * fix: Namespace Sync controller should list no resources when source namespace is empty string by @dlipovetsky in #725 * fix: Temporarily hard-code supported PC version for Nutanix CSI by @jimmidyson in #751 * fix: skip kubeadm CA file when Secret doesn't have a CA by @dkoshkin in #752 * fix: Correctly report failed deploy of ServiceLoadBalancer by @dlipovetsky in #759 ### Other Changes * build: Tidy up goreleaser config by @jimmidyson in #745 * ci: Fix up image loading for lint-test-helm by @jimmidyson in #746 * refactor: Tidy up Nutanix CSI with consistent apply strategy by @jimmidyson in #733 * test(e2e): Set empty env vars for Nutanix e2e vars by @jimmidyson in #749 * refactor: Use recommended "default" function syntax in helm templates by @dlipovetsky in #750 * refactor: Reusable HelmAddon strategy by @jimmidyson in #735 * test(e2e): Various e2e tests fixes by @jimmidyson in #754 * test(e2e): Correct default helm release names for AWS CCM and EBS CSI by @jimmidyson in #756 **Full Changelog**: v0.10.0...v0.11.0 --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently both Nutanix CSI and AWS EBS CSI handlers deploy the
snapshot-controller. Generally the snapshot-controller should be
treated as a separate addon that all compatible CSI providers can
take advantage of.
This commit removes the snapshot-controller from both Nutanix and
AWS EBS CSI, and instead deploys the snapshot-controller separately
so they can both use it as necessary.
Deployment tested manually on AWS via e2e test suite as well as the
automated Docker test suite running in CI.
Depends on #733.