Difference between revisions of "Kubernetes Server-Side apply"
Jump to navigation
Jump to search
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | * https://kubernetes.io/docs/reference/using-api/server-side-apply/ | + | * https://kubernetes.io/docs/reference/using-api/server-side-apply/ (Aug 2021, [[Kubernetes v1.22]] [stable]) |
| + | If you have Server-Side Apply enabled, the control plane tracks managed fields for all newly created objects. | ||
| + | |||
| Line 6: | Line 8: | ||
[[kubectl apply --server-side]] | [[kubectl apply --server-side]] | ||
| + | [[ManagedFields:]] | ||
| + | |||
| + | |||
| + | == Related == | ||
| + | [[last-applied]] | ||
| + | [[kube-controller-manager]] | ||
| + | [[Kubernetes Topology Manager]] | ||
| + | |||
| + | == See also == | ||
| + | * {{kubectl apply}} | ||
| − | + | [[Category:K8s]] | |
Latest revision as of 15:37, 5 December 2022
- https://kubernetes.io/docs/reference/using-api/server-side-apply/ (Aug 2021, Kubernetes v1.22 [stable])
If you have Server-Side Apply enabled, the control plane tracks managed fields for all newly created objects.
kubectl apply --server-side
ManagedFields:
Related[edit]
last-applied kube-controller-manager Kubernetes Topology Manager
See also[edit]
Advertising:
