Difference between revisions of "Operation cannot be fulfilled on"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
− | + | == Related == | |
{{is missing}} | {{is missing}} | ||
Revision as of 14:53, 9 August 2023
for: ".\\xxxxxx.yaml": Operation cannot be fulfilled on ingresses.networking.k8s.io "yourtext": the object has been modified; please apply your changes to the latest version and try again
Related
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
kubectl apply, --server-side, -k, -f, creationTimestamp, kubectl.kubernetes.io/last-applied-configuration, --validate=false
k8s.io, kubectl api-versions, kubernetes.io, networking.k8s.io, scheduling.k8s.io/v1, apiextensions.k8s.io, k8s.io/cluster-autoscaler/, rbac.authorization.k8s.io/v1, authentication.k8s.io, storage.k8s.io, metrics.k8s.io, discovery.k8s.io, csi.k8s.io, registry.k8s.io, pkgs.k8s.io, apiserver.k8s.io, audit.k8s.io, admissionregistration.k8s.io
Advertising: