We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What happened: cloneset-nginx.yaml
kubectl apply -f cloneset-nginx.yaml -n kruise
apiVersion: apps.kruise.io/v1alpha1 kind: CloneSet metadata: labels: app: nginx name: nginx spec: replicas: 5 selector: matchLabels: app: nginx template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:alpine
wls/wls-subsets-preferredNodeSelectorTerms-preference-matchFields.yaml
apiVersion: apps.kruise.io/v1alpha1 kind: WorkloadSpread metadata: name: wls spec: targetRef: apiVersion: apps.kruise.io/v1alpha1 kind: CloneSet name: nginx subsets: - name: subset-a maxReplicas: 2 requiredNodeSelectorTerm: matchExpressions: - key: topology.kubernetes.io/zone operator: In values: - z3 preferredNodeSelectorTerms: - preference: matchFields: - key: metadata.name operator: In values: - 192.168.229.128 weight: 100 - name: subset-b requiredNodeSelectorTerm: matchExpressions: - key: topology.kubernetes.io/zone operator: In values: - z2
kubectl label node 192.168.229.128 topology.kubernetes.io/zone=z3 --overwrite kubectl label node 192.168.229.129 topology.kubernetes.io/zone=z3 --overwrite kubectl label node 192.168.229.130 topology.kubernetes.io/zone=z2 --overwrite kubectl label node 192.168.229.128 topology.istio.io/subzone=sz01 --overwrite kubectl label node 192.168.229.129 topology.istio.io/subzone=sz02 --overwrite kubectl label node 192.168.229.130 topology.istio.io/subzone=sz03 --overwrite kubectl apply -f wls-subsets-preferredNodeSelectorTerms-preference-matchFields.yaml -n kruise kubectl kruise rollout restart cloneset nginx -n kruise C[root@node01 wls]# kubectl get pod -n kruise -owide -w NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES nfs-client-provisioner-69557bfdb8-hzplg 0/1 Unknown 0 99d <none> 192.168.229.128 <none> <none> nginx-48h42 1/1 Running 0 3m42s 172.20.2.27 192.168.229.130 <none> 2/2 nginx-8hkmx 1/1 Running 0 2m54s 172.20.2.29 192.168.229.130 <none> 2/2 nginx-9wn2q 1/1 Running 0 3m43s 172.20.2.26 192.168.229.130 <none> 2/2 nginx-xskqc 1/1 Running 0 3m10s 172.20.0.131 192.168.229.128 <none> 2/2 nginx-zqs5f 1/1 Running 0 3m26s 172.20.2.28 192.168.229.130 <none> 2/2
128,129只有一个,不是max为2个么
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
The text was updated successfully, but these errors were encountered:
@13567436138 Please ensure that you have enabled the WorkloadSpread feature-gate when installing kruise.
WorkloadSpread
Sorry, something went wrong.
Maybe, your problem is similar with #1194.
This problem will be fixed after #1197 is merged.
veophi
No branches or pull requests
What happened:
cloneset-nginx.yaml
kubectl apply -f cloneset-nginx.yaml -n kruise
wls/wls-subsets-preferredNodeSelectorTerms-preference-matchFields.yaml
128,129只有一个,不是max为2个么
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: