-
Notifications
You must be signed in to change notification settings - Fork 33
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
[ISSUE-802] Proposal for deploying csi on k3s #806
[ISSUE-802] Proposal for deploying csi on k3s #806
Conversation
Signed-off-by: Dutova <Ann.Dutova@Dell.com>
Signed-off-by: Dutova <Ann.Dutova@Dell.com>
Codecov Report
@@ Coverage Diff @@
## master #806 +/- ##
==========================================
- Coverage 71.91% 71.88% -0.04%
==========================================
Files 61 61
Lines 6139 6142 +3
==========================================
Hits 4415 4415
- Misses 1479 1481 +2
- Partials 245 246 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
2. Pass it to the k3s application server with appropriate flag | ||
3. Reload daemon | ||
4. Test with temp pod | ||
|
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.
I guess we should mention steps for CSI Uninstallation too
- Rename proposal - Rephrase background section - Change purpose - Add all commands - Add Rationale section - Mention Uninstall CSI in tasks Signed-off-by: Dutova <Ann.Dutova@Dell.com>
Signed-off-by: Dutova <Ann.Dutova@Dell.com>
Should this branch contain the changes necessary for automation? |
No, just a proposal for the beggining |
Signed-off-by: Dutova <Ann.Dutova@Dell.com>
Purpose
Resolves #802
Add proposal for discussion steps of deploying csi on k3s
PR checklist
Testing
k3s server log: