-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
[1.7] Automated cherry pick of #58720 #60342 #60516
[1.7] Automated cherry pick of #58720 #60342 #60516
Conversation
Add a feature gate ReadOnlyAPIDataVolumes to a provide a way to disable the new behavior in 1.10, but for 1.11, the new behavior will become non-optional. Also, update E2E tests for downwardAPI and projected volumes to mount the volumes somewhere other than /etc.
Since the runtime may try to create mount points within the sandbox, it will fail if the mount point is within a read-only API data volume, like a secret or configMap volume. Create any needed mount points during volume setup.
3013c5f
to
e13121a
Compare
/kind bug |
One of the failed tests is marked flaky, so retrying: |
/lgtm |
/assign @wojtek-t |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: joelsmith, msau42, smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This still needs cherry pick approval |
Cherrypick approved. |
/test all [submit-queue is verifying that this PR is safe to merge] |
/retest |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Cherry pick of #58720 #60342 on release-1.7.
#58720: Ensure that the runtime mounts RO volumes read-only
#60342: Fix nested volume mounts for read-only API data volumes
Fixes #60814 for 1.7