UPSTREAM: 60342: Fix nested volume mounts for read-only API data volumes #18766
Conversation
openshift-ci-robot
added
the
size/L
openshift-merge-robot
added
the
vendor-update
|
/retest |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: joelsmith, jsafrane, sjenning 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 |
openshift-ci-robot
added
the
approved
|
/test unit |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
/test extended_networking_minimal |
|
/cherrypick release-3.9 |
|
@joelsmith: once the present PR merges, I will cherry-pick it on top of release-3.9 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Automatic merge from submit-queue. |
|
@joelsmith: new pull request created: #18789 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
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.
xref kubernetes/kubernetes#60342
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Release note:
No release notes because we haven't released anything (yet) that has this bug.