Open dayongi opened 1 year ago
@dayongi: This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Does this only happen with kubectl
, or do the symptoms also show up when making a request using (eg) curl
?
Does this only happen with
kubectl
, or do the symptoms also show up when making a request using (eg)curl
?
I only tried it with kubectl
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Hi, can you please verify this on a newer version of kubectl? Either 1.30 or 1.29. If it is still an issue on those versions, could you please provide a simpler example of how to observe the issue?
/triage needs-information /remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
What happened: When using the add operator of JSON Patch to modify the CRD, it is found that the original value is overwritten instead of appended
What you expected to happen: Append the desired value to the corresponding property.
How to reproduce it (as minimally and precisely as possible): 1、This is the initial declaration for the corresponding CRD:
2、This is the instruction of the executed JSON Patch:
From the final result, it can be found that after the Patch command is executed, the required value is not added to the corresponding attribute, but the value of the original attribute is overwritten. What is the problem?
Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):