change replicaset documentation to use apps/v1 APIs
This commit is contained in:
@@ -1,4 +1,4 @@
|
|||||||
apiVersion: apps/v1beta2 # for versions before 1.8.0 use apps/v1beta1
|
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
|
||||||
kind: ReplicaSet
|
kind: ReplicaSet
|
||||||
metadata:
|
metadata:
|
||||||
name: frontend
|
name: frontend
|
||||||
|
|||||||
@@ -126,7 +126,7 @@ deleted. This allows the ReplicaSet to be replaced without affecting the running
|
|||||||
The `.spec.template.metadata.labels` must match the `.spec.selector`, or it will
|
The `.spec.template.metadata.labels` must match the `.spec.selector`, or it will
|
||||||
be rejected by the API.
|
be rejected by the API.
|
||||||
|
|
||||||
In Kubernetes 1.8 the API version `apps/v1beta2` on the ReplicaSet kind is the current version and is enabled by default. The API version `extensions/v1beta1` is deprecated. In API version `apps/v1beta2`, `.spec.selector` and `.metadata.labels` no longer default to `.spec.template.metadata.labels` if not set. So they must be set explicitly. Also note that `.spec.selector` is immutable after creation starting in API version `apps/v1beta2`.
|
In Kubernetes 1.9 the API version `apps/v1` on the ReplicaSet kind is the current version and is enabled by default. The API version `apps/v1beta2` is deprecated.
|
||||||
|
|
||||||
Also you should not normally create any pods whose labels match this selector, either directly, with
|
Also you should not normally create any pods whose labels match this selector, either directly, with
|
||||||
another ReplicaSet, or with another controller such as a Deployment. If you do so, the ReplicaSet thinks that it
|
another ReplicaSet, or with another controller such as a Deployment. If you do so, the ReplicaSet thinks that it
|
||||||
|
|||||||
Reference in New Issue
Block a user