Skip to content

chore(virtiofs): Drop feature gate EnableVirtioFsConfigVolumes #937

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.

Sign up for GitHub

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

chore(virtiofs): Drop feature gate EnableVirtioFsConfigVolumes #937

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions docs/storage/disks_and_volumes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1001,8 +1001,6 @@ status: {}
By using filesystem, `configMaps` are shared through `virtiofs`. In contrast with using disk for sharing `configMaps`,
`filesystem` allows you to dynamically propagate changes on `configMaps` to VMIs (i.e. the VM does not need to be rebooted).

> **Note:** You need to enable the feature gate `EnableVirtioFsConfigVolumes` for sharing `configMaps` with `virtiofs`.

To share a given `configMap`, the following VM definition could be used:

```yaml
Expand Down Expand Up @@ -1127,8 +1125,6 @@ status: {}
By using filesystem, `secrets` are shared through `virtiofs`. In contrast with using disk for sharing `secrets`,
`filesystem` allows you to dynamically propagate changes on `secrets` to VMIs (i.e. the VM does not need to be rebooted).

> **Note:** You need to enable the feature gate `EnableVirtioFsConfigVolumes` for sharing `secrets` with `virtiofs`.

To share a given `secret`, the following VM definition could be used:

```yaml
Expand Down Expand Up @@ -1228,8 +1224,6 @@ spec:
By using filesystem, `serviceAccounts` are shared through `virtiofs`. In contrast with using disk for sharing `serviceAccounts`,
`filesystem` allows you to dynamically propagate changes on `serviceAccounts` to VMIs (i.e. the VM does not need to be rebooted).

> **Note:** You need to enable the feature gate `EnableVirtioFsConfigVolumes` for sharing `serviceAccounts` with `virtiofs`.

To share a given `serviceAccount`, the following VM definition could be used:

```yaml
Expand Down