kubernetes/kubernetes
kubectl edit fail, since deploy contains imagePullSecrets: - {}
オープン
#109,953 opened on 2022/05/11
help wantedkind/bugsig/api-machinerysig/clitriage/accepted
Repository metrics
- Stars
- (122,268 個のスター)
- PR merge metrics
- (平均マージ 28d 17h) (30d で 343 merged PRs)
説明
What happened?
if a deploy contains:
spec:
imagePullSecrets:
- {}
it will cause kubectl edit fail, although kubectl create success.
some people meet the same problem:
https://stackoverflow.com/questions/49694153/kubernetes-error-kubectl-edit-deployment
the scheduler suffer the problem, happen and fix in 1.20.x
https://github.com/kubernetes/kubernetes/commit/bd5c54805d4fef12cf056440cbd3b7f06afef8e5
although patchStatus can fix the scheduler problem, it can not fix demand that patch spec.
What did you expect to happen?
consistency: if kubectl edit fail, means patch fail, the kubectl create need fail too.
How can we reproduce it (as minimally and precisely as possible)?
valid deploy create, and stop using "-: {}"
Anything else we need to know?
No response
Kubernetes version
$ kubectl version
# paste output here
Cloud provider
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here