-
Notifications
You must be signed in to change notification settings - Fork 23
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
Set the volume mount's readonly annotation based on the ISVC annotation #388
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hdefazio The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d7ee13b
to
36bedac
Compare
cea990e
to
5617856
Compare
efec407
to
ca97846
Compare
@terrytangyuan this changes looks ok, do you want to take another look? |
@spolti do you mean to tag me here? not sure if this relate to the work i do. |
This PR is still in draft. Is it ready for review? |
I mentioned previously that we'll need the upstream to review this as well. Do we have a PR in upstream? |
expected: &v1.Pod{ | ||
ObjectMeta: metav1.ObjectMeta{ | ||
Annotations: map[string]string{ | ||
constants.StorageInitializerSourceUriInternalAnnotationKey: "gs://foo", |
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.
@spolti Just curious - does the readonly annotation key get dropped when the pod is created? Or should that field be here too? (the test isn't failing as-is)
Sry, wrong tag =/ |
@terrytangyuan This is ready for review now |
Signed-off-by: Hannah DeFazio <[email protected]>
Signed-off-by: Hannah DeFazio <[email protected]>
Signed-off-by: Hannah DeFazio <[email protected]>
Closing in favor of kserve#3885 |
What this PR does / why we need it:
Fixes kserve#3687
https://issues.redhat.com/browse/RHOAIENG-8288
Type of changes
Bug fix (non-breaking change which fixes an issue)
Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.
Test Setup:
Test Cases:
storage.kserve.io/readonly: "false"
storage.kserve.io/readonly: "true"
storage.kserve.io/readonly was not provided
Special notes for your reviewer:
Checklist:
Release note:
Re-running failed tests
/rerun-all
- rerun all failed workflows./rerun-workflow <workflow name>
- rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.