Skip to content

ContainerPath Volumes User Guide#999

Open
mhenriks wants to merge 1 commit into
kubevirt:mainfrom
mhenriks:containerpath-volumes-docs
Open

ContainerPath Volumes User Guide#999
mhenriks wants to merge 1 commit into
kubevirt:mainfrom
mhenriks:containerpath-volumes-docs

Conversation

@mhenriks

Copy link
Copy Markdown
Member

What this PR does / why we need it:

Doc for ContainerPath Volumes

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:

ContainerPath Volumes User Guide

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label May 27, 2026
@kubevirt-bot kubevirt-bot requested review from ShellyKa13 and awels May 27, 2026 20:51
@kubevirt-bot kubevirt-bot added size/L needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 27, 2026
@kubevirt-bot

Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

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-sigs/prow repository.

@jean-edouard jean-edouard left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

Comment on lines +133 to +135
**Why both volumes?**
- `sa-volume`: Ensures the virt-launcher pod uses the IRSA-annotated ServiceAccount, which triggers token injection.
- `aws-token`: Exposes the injected EKS token path to the VM via virtiofs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formatting: these 3 lines show as 1 line in the preview

Comment thread docs/storage/containerpath_volumes.md Outdated
- The specified `path` must be an absolute path that exists within the virt-launcher pod's `compute` container
- The path must correspond to (or be a subpath of) a volumeMount in the compute container
- The path should exist before VM startup, or be continuously populated by a sidecar or webhook-injected mechanism
- Paths containing `..` components that would escape the volumeMount boundary are rejected

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Symlinks that escape the volumeMount are rejected too, right?

@kubevirt-bot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jean-edouard

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 8, 2026
Add documentation for the ContainerPath volumes feature (VEP 165),
which allows VMs to access files dynamically injected into the
virt-launcher pod via virtiofs. Includes examples for AWS IRSA and
Azure Workload Identity.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Michael Henriksen <mhenriks@redhat.com>
@mhenriks mhenriks force-pushed the containerpath-volumes-docs branch from d2bc154 to 8320b57 Compare June 8, 2026 19:40
@dhiller dhiller removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants