Open zhangzhiqiangcs opened 9 months ago
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
@zhangzhiqiangcs: The label(s) sig/kubectl
cannot be applied, because the repository doesn't have them.
/sig cli
/transfer kubectl
Could you please explain the steps you took to reproduce this?
@Ithrael Hi, here is the example sts, I just change the labels on the volumeClaimTemplates
. Apply a1.yaml, and then use kubectl diff -f a1.yaml
a1.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: myapp
spec:
selector:
matchLabels:
app: myapp
serviceName: myapp
replicas: 2
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: myapp
image: registry.k8s.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
volumeMounts:
- name: www
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: www
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 1Gi
a2.yaml
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: myapp
spec:
selector:
matchLabels:
app: myapp
serviceName: myapp
replicas: 2
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: myapp
image: registry.k8s.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
volumeMounts:
- name: www
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: www
labels:
app: myapp
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 1Gi
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 would you like to be added?
when statefulset patch is failed, kubectl output the the patch informations, not just output something like
Why is this needed?
some patch information may help user to understand why patch is failed, it is useful when the actual diff is not so obvious