-
Notifications
You must be signed in to change notification settings - Fork 29
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
genpolicy: support dynamic SMB storage class options #245
Conversation
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.
LGTM once feedback has been resolved :)
e4b7f7d
to
1ee16b0
Compare
1ee16b0
to
f1fb8f1
Compare
- Update mount_and_storage.rs and stateful_set.rs to support dynamic SMB storage class options. - Update SMB storage class options in genpolicy-settings.json. - Update rules.rego to support dynamic SMB storage class options. Signed-off-by: Archana Choudhary <[email protected]>
a9c0dac
to
dd6342c
Compare
Adapt samples for dynamic SMB changes. Signed-off-by: Saul Paredes <[email protected]>
Looks good, thanks @arc9693 ! |
"cc-azurefile-csi", | ||
"cc-azurefile-premium-csi" | ||
{ | ||
"name": "azurefile-csi-kata-cc", |
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.
We probably want to use azurefile-csi
and azurefile-premium-csi
since we want the official driver to support conf pods?
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.
The default storage drivers do not have enableKataCCMount set to true.
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 agree with @sprt, it would be good to include the default Azure File storage classes. For example, our team creates a custom storage class with name azurefile-csi
and set the enableKataCCMount
flag to true; we use the same name for compatibility with non-confidential deployments. Adding them would also align with the plan of removing the flag from the storage class and automatically enabling kata mount for confidential pods in the Azure File CSI driver.
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.
To be added, post migration discussion with Andy. As of now, it's not true by default for azurefile-csi. So, to reduce conflict we will keep as it is for now.
Did we ensure that this change does not regress our Azure Disk and Azure Local drivers? |
Closing this after discussion yesterday @sprt. |
Merge Checklist
upstream/missing
label (orupstream/not-needed
) has been set on the PR.Summary
work item: https://microsoft.visualstudio.com/OS/_workitems/edit/54514252
Test Methodology