kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #32625 from tengqm/AnyVolumeDataSource-beta 

AnyVolumeDataSource feature is now Beta
This commit is contained in:
Kubernetes Prow Robot 2022-03-31 14:43:06 -07:00 committed by GitHub
parent ef745a03be fa95fa9b23
commit a3be045946
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/en/docs/concepts/storage/persistent-volumes.md
View File

@ -904,17 +904,12 @@ spec:
## Volume populators and data sources ## Volume populators and data sources
{{< feature-state for_k8s_version="v1.22" state="alpha" >}} {{< feature-state for_k8s_version="v1.24" state="beta" >}}
{{< note >}} Kubernetes supports custom volume populators.
Kubernetes supports custom volume populators; this alpha feature was introduced
in Kubernetes 1.18. Kubernetes 1.22 reimplemented the mechanism with a redesigned API.
Check that you are reading the version of the Kubernetes documentation that matches your
cluster. {{% version-check %}}
To use custom volume populators, you must enable the `AnyVolumeDataSource` To use custom volume populators, you must enable the `AnyVolumeDataSource`
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) for
the kube-apiserver and kube-controller-manager. the kube-apiserver and kube-controller-manager.
{{< /note >}}
Volume populators take advantage of a PVC spec field called `dataSourceRef`. Unlike the Volume populators take advantage of a PVC spec field called `dataSourceRef`. Unlike the
`dataSource` field, which can only contain either a reference to another PersistentVolumeClaim `dataSource` field, which can only contain either a reference to another PersistentVolumeClaim
@ -932,6 +927,7 @@ contents.
There are two differences between the `dataSourceRef` field and the `dataSource` field that There are two differences between the `dataSourceRef` field and the `dataSource` field that
users should be aware of: users should be aware of:
* The `dataSource` field ignores invalid values (as if the field was blank) while the * The `dataSource` field ignores invalid values (as if the field was blank) while the
`dataSourceRef` field never ignores values and will cause an error if an invalid value is `dataSourceRef` field never ignores values and will cause an error if an invalid value is
used. Invalid values are any core object (objects with no apiGroup) except for PVCs. used. Invalid values are any core object (objects with no apiGroup) except for PVCs.

3
content/en/docs/reference/command-line-tools-reference/feature-gates.md
View File

@ -61,7 +61,8 @@ different Kubernetes components.
| `APIServerIdentity` | `false` | Alpha | 1.20 | | | `APIServerIdentity` | `false` | Alpha | 1.20 | |
| `APIServerTracing` | `false` | Alpha | 1.22 | | | `APIServerTracing` | `false` | Alpha | 1.22 | |
| `AllowInsecureBackendProxy` | `true` | Beta | 1.17 | | | `AllowInsecureBackendProxy` | `true` | Beta | 1.17 | |
| `AnyVolumeDataSource` | `false` | Alpha | 1.18 | | | `AnyVolumeDataSource` | `false` | Alpha | 1.18 | 1.23 |
| `AnyVolumeDataSource` | `true` | Beta | 1.24 | |
| `AppArmor` | `true` | Beta | 1.4 | | | `AppArmor` | `true` | Beta | 1.4 | |
| `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | 1.21 | | `ControllerManagerLeaderMigration` | `false` | Alpha | 1.21 | 1.21 |
| `ControllerManagerLeaderMigration` | `true` | Beta | 1.22 | | | `ControllerManagerLeaderMigration` | `true` | Beta | 1.22 | |