Difference between revisions of "Kubectl create --save-config"
Jump to navigation
Jump to search
(Created page with "{{lc}} {{is missing}} {{kubectl create}}") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| + | --save-config=false: | ||
| + | If true, the configuration of current object will be saved in its | ||
| + | annotation. Otherwise, the [[annotation]] will be unchanged. This flag is | ||
| + | useful when you want to perform kubectl apply on this object in the | ||
| + | future. | ||
| + | == Related == | ||
| + | * [[creationTimestamp]] | ||
| + | {{is missing}} | ||
| − | + | == See also == | |
| − | + | * {{kubectl create}} | |
| − | |||
| − | {{kubectl create}} | ||
Latest revision as of 15:10, 9 August 2023
--save-config=false: If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future.
Related[edit]
Warning: resource configmaps/kube-root-ca.crt is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically. secret/default-token-7z4zd created Error from server (Conflict): error when applying patch: .../... to: Resource: "/v1, Resource=configmaps", GroupVersionKind: "/v1, Kind=ConfigMap" Name: "kube-root-ca.crt", Namespace: "your-namespace" for: "your.yaml": Operation cannot be fulfilled on configmaps "kube-root-ca.crt": the object has been modified; please apply your changes to the latest version and try again
See also[edit]
kubectl create [ namespace | secret | deployment | configmap | service | role ]--help
Advertising:
