@@ -700,9 +700,12 @@ spec:
700
700
provisioner or an external controller can support
701
701
the specified data source, it will create a new
702
702
volume based on the contents of the specified
703
- data source. If the AnyVolumeDataSource feature
704
- gate is enabled, this field will always have the
705
- same contents as the DataSourceRef field.'
703
+ data source. When the AnyVolumeDataSource feature
704
+ gate is enabled, dataSource contents will be copied
705
+ to dataSourceRef, and dataSourceRef contents will
706
+ be copied to dataSource when dataSourceRef.namespace
707
+ is not specified. If the namespace is specified,
708
+ then dataSourceRef will not be copied to dataSource.'
706
709
properties :
707
710
apiGroup :
708
711
description : APIGroup is the group for the resource
@@ -727,27 +730,35 @@ spec:
727
730
description : ' dataSourceRef specifies the object
728
731
from which to populate the volume with data, if
729
732
a non-empty volume is desired. This may be any
730
- local object from a non-empty API group (non core
731
- object) or a PersistentVolumeClaim object. When
732
- this field is specified, volume binding will only
733
- succeed if the type of the specified object matches
734
- some installed volume populator or dynamic provisioner.
733
+ object from a non-empty API group (non core object)
734
+ or a PersistentVolumeClaim object. When this field
735
+ is specified, volume binding will only succeed
736
+ if the type of the specified object matches some
737
+ installed volume populator or dynamic provisioner.
735
738
This field will replace the functionality of the
736
- DataSource field and as such if both fields are
739
+ dataSource field and as such if both fields are
737
740
non-empty, they must have the same value. For
738
- backwards compatibility, both fields (DataSource
739
- and DataSourceRef) will be set to the same value
741
+ backwards compatibility, when namespace isn'' t
742
+ specified in dataSourceRef, both fields (dataSource
743
+ and dataSourceRef) will be set to the same value
740
744
automatically if one of them is empty and the
741
- other is non-empty. There are two important differences
742
- between DataSource and DataSourceRef: * While
743
- DataSource only allows two specific types of objects,
744
- DataSourceRef allows any non-core object, as well
745
- as PersistentVolumeClaim objects. * While DataSource
746
- ignores disallowed values (dropping them), DataSourceRef
747
- preserves all values, and generates an error if
748
- a disallowed value is specified. (Beta) Using
749
- this field requires the AnyVolumeDataSource feature
750
- gate to be enabled.'
745
+ other is non-empty. When namespace is specified
746
+ in dataSourceRef, dataSource isn'' t set to the
747
+ same value and must be empty. There are three
748
+ important differences between dataSource and dataSourceRef:
749
+ * While dataSource only allows two specific types
750
+ of objects, dataSourceRef allows any non-core
751
+ object, as well as PersistentVolumeClaim objects.
752
+ * While dataSource ignores disallowed values (dropping
753
+ them), dataSourceRef preserves all values, and
754
+ generates an error if a disallowed value is specified.
755
+ * While dataSource only allows local objects,
756
+ dataSourceRef allows objects in any namespaces.
757
+ (Beta) Using this field requires the AnyVolumeDataSource
758
+ feature gate to be enabled. (Alpha) Using the
759
+ namespace field of dataSourceRef requires the
760
+ CrossNamespaceVolumeDataSource feature gate to
761
+ be enabled.'
751
762
properties :
752
763
apiGroup :
753
764
description : APIGroup is the group for the resource
@@ -764,6 +775,17 @@ spec:
764
775
description : Name is the name of resource being
765
776
referenced
766
777
type : string
778
+ namespace :
779
+ description : Namespace is the namespace of resource
780
+ being referenced Note that when a namespace
781
+ is specified, a gateway.networking.k8s.io/ReferenceGrant
782
+ object is required in the referent namespace
783
+ to allow that namespace's owner to accept
784
+ the reference. See the ReferenceGrant documentation
785
+ for details. (Alpha) This field requires the
786
+ CrossNamespaceVolumeDataSource feature gate
787
+ to be enabled.
788
+ type : string
767
789
required :
768
790
- kind
769
791
- name
@@ -776,6 +798,30 @@ spec:
776
798
value but must still be higher than capacity recorded
777
799
in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources'
778
800
properties :
801
+ claims :
802
+ description : " Claims lists the names of resources,
803
+ defined in spec.resourceClaims, that are used
804
+ by this container. \n This is an alpha field
805
+ and requires enabling the DynamicResourceAllocation
806
+ feature gate. \n This field is immutable."
807
+ items :
808
+ description : ResourceClaim references one
809
+ entry in PodSpec.ResourceClaims.
810
+ properties :
811
+ name :
812
+ description : Name must match the name
813
+ of one entry in pod.spec.resourceClaims
814
+ of the Pod where this field is used.
815
+ It makes that resource available inside
816
+ a container.
817
+ type : string
818
+ required :
819
+ - name
820
+ type : object
821
+ type : array
822
+ x-kubernetes-list-map-keys :
823
+ - name
824
+ x-kubernetes-list-type : map
779
825
limits :
780
826
additionalProperties :
781
827
anyOf :
@@ -1758,8 +1804,8 @@ spec:
1758
1804
description : " Condition contains details for one aspect of the current
1759
1805
state of this API Resource. --- This struct is intended for direct
1760
1806
use as an array at the field path .status.conditions. For example,
1761
- type FooStatus struct{ // Represents the observations of a foo's
1762
- current state. // Known .status.conditions.type are: \" Available\" ,
1807
+ \n type FooStatus struct{ // Represents the observations of a
1808
+ foo's current state. // Known .status.conditions.type are: \" Available\" ,
1763
1809
\" Progressing\" , and \" Degraded\" // +patchMergeKey=type // +patchStrategy=merge
1764
1810
// +listType=map // +listMapKey=type Conditions []metav1.Condition
1765
1811
`json:\" conditions,omitempty\" patchStrategy:\" merge\" patchMergeKey:\" type\"
0 commit comments