Skip to content
New issue

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

Only one node extends the volume #212

Closed
garenchan opened this issue Jul 7, 2022 · 1 comment
Closed

Only one node extends the volume #212

garenchan opened this issue Jul 7, 2022 · 1 comment

Comments

@garenchan
Copy link

garenchan commented Jul 7, 2022

I am now using SeaweedFS with seaweedfs-csi-driver on K8S.

I created a persistent volume claim seaweedfs-dynamic with storage class seaweedfs-storage.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: seaweedfs-dynamic
spec:
  storageClassName: "seaweedfs-storage"
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 100Gi

And I created 2 pods to use the pvc seaweedfs-dynamic, and these 2 pods were scheduled on 2 nodes.

kind: Pod
apiVersion: v1
metadata:
  name: pod1
spec:
  containers:
    - name: frontend
      image: busybox
      volumeMounts:
        - mountPath: "/data"
          name: seaweedfs-volume
      command: [ "sleep", "1000000" ]
  volumes:
    - name: seaweedfs-volume
      persistentVolumeClaim:
        claimName: seaweedfs-dynamic
  nodeName: 152-worker-0b2e90
---
kind: Pod
apiVersion: v1
metadata:
  name: pod2
spec:
  containers:
    - name: frontend
      image: busybox
      volumeMounts:
        - mountPath: "/data"
          name: seaweedfs-volume
      command: [ "sleep", "1000000" ]
  volumes:
    - name: seaweedfs-volume
      persistentVolumeClaim:
        claimName: seaweedfs-dynamic
  nodeName: 151-worker-7add5d

Finally, I tried to change the storage size of pvc to 200GB. But only the driver on node 152-worker-0b2e90 received the NodeExpandVolume request and expanded the volume.

I'm using version v1.16.13 of K8S and version v1.1.0 of the csi-resizer image .

# kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:38:50Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.13", GitCommit:"39a145ca3413079bcb9c80846488786fed5fe1cb", GitTreeState:"clean", BuildDate:"2020-07-15T16:10:14Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.16) exceeds the supported minor version skew of +/-1

# cat value.yaml
k8s.gcr.io/sig-storage/csi-resizer:v1.1.0
@gnufied
Copy link
Contributor

gnufied commented Jul 7, 2022

If you upgrade to v1.24 version of k8s, this behaviour should be fixed and expansion should be called on all nodes. See - kubernetes/kubernetes#108693

@gnufied gnufied closed this as completed Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants