-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add support for CSI driver in CKS #11419
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
base: main
Are you sure you want to change the base?
Conversation
This pull request has merge conflicts. Dear author, please fix the conflicts and sync your branch with the base branch. |
…support-csi-projects
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #11419 +/- ##
============================================
- Coverage 17.35% 17.34% -0.02%
- Complexity 15230 15271 +41
============================================
Files 5886 5886
Lines 525685 527568 +1883
Branches 64159 65017 +858
============================================
+ Hits 91247 91493 +246
- Misses 424138 425753 +1615
- Partials 10300 10322 +22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@blueorangutan package |
4fb7b37
to
4e53e96
Compare
@blueorangutan package |
@kiranchavala a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 14731 |
|
Description
This PR adds support to deploy the CSI driver when deploying CKS clusters. It isn't setup by default, only done when the enablecsi parameter is passed. Also added support for snapshot related APIs for the project level user to allow snapshots of persistent volumes at project level
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?