您在ACK集羣中使用alicloud-nas-controller時，如果安裝的版本較低，可以通過如下方式升級組件：
當前集羣狀態：
如果您使用的nas controller是早期版本，如下：
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
labels:
app: alicloud-nas-controller
name: alicloud-nas-controller
namespace: kube-system
spec:
selector:
matchLabels:
app: alicloud-nas-controller
template:
metadata:
labels:
app: alicloud-nas-controller
spec:
containers:
- env:
- name: PROVISIONER_NAME
value: alicloud/nas
- name: NFS_SERVER
value: 2564f49129-**.cn-shenzhen.nas.aliyuncs.com
- name: NFS_PATH
value: /
image: registry.cn-hangzhou.aliyuncs.com/acs/alicloud-nas-controller:v3.1.0-k8s1.11
imagePullPolicy: IfNotPresent
name: alicloud-nas-controller
volumeMounts:
- mountPath: /persistentvolumes
name: nfs-client-root
serviceAccount: admin
serviceAccountName: admin
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/master
operator: Exists
- effect: NoSchedule
key: node.cloudprovider.kubernetes.io/uninitialized
operator: Exists
volumes:
- flexVolume:
driver: alicloud/nas
options:
path: /
server: 2564f49129-**.cn-shenzhen.nas.aliyuncs.com
vers: "4.0"
name: nfs-client-rootStorageClass配置如下：
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: alicloud-nas
mountOptions:
- vers=4.0
provisioner: alicloud/nas
reclaimPolicy: Retain集羣中有應用使用上述controller配置創建了pvc/pv，並掛載到pod中使用：
# kubectl describe pod web-nas-1 | grep ClaimName
ClaimName: html-web-nas-1
# kubectl get pvc html-web-nas-1
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
html-web-nas-1 Bound pvc-2612b272-14e7-11ea-a9b7-00163e084110 2Gi RWO alicloud-nas 85m
這時pv的配置爲v4版本；
# kubectl get pv pvc-2612b272-14e7-11ea-a9b7-00163e084110 -oyaml | grep mountOptions -A 6
mountOptions:
- vers=4.0
nfs:
path: /default-html-web-nas-1-pvc-2612b272-14e7-11ea-a9b7-00163e084110
server: 2564f49129-**.cn-shenzhen.nas.aliyuncs.com
persistentVolumeReclaimPolicy: Retain
storageClassName: alicloud-nasPV新訴求
登陸Pod所在節點，查看掛載nas的參數爲：
# mount | grep nfs
2564f49129-**.cn-shenzhen.nas.aliyuncs.com:/default-html-web-nas-1-pvc-2612b272-14e7-11ea-a9b7-00163e084110 on /var/lib/kubelet/pods/32222e36-14f2-11ea-a9b7-00163e084110/volumes/kubernetes.io~nfs/pvc-2612b272-14e7-11ea-a9b7-00163e084110 type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.25,local_lock=none,addr=192.168.1.152)如果你希望更新nas掛載參數，期望修改pv的mountOptions參數，例如配置爲下面參數：
- nolock,tcp,noresvport
- vers=3執行編輯命令：
# kubectl edit pv pvc-2612b272-14e7-11ea-a9b7-00163e084110將mountOptions參數更新爲：
mountOptions:
- nolock,tcp,noresvport
- vers=3重啓Pod：
# kubectl delete pod web-nas-1
登陸Pod所在節點插件nas掛載參數：可見已經配置了noresvport等參數；
# mount | grep nfs
2564f49129-**.cn-shenzhen.nas.aliyuncs.com:/default-html-web-nas-1-pvc-2612b272-14e7-11ea-a9b7-00163e084110 on /var/lib/kubelet/pods/ba374a37-14f3-11ea-a9b7-00163e084110/volumes/kubernetes.io~nfs/pvc-2612b272-14e7-11ea-a9b7-00163e084110 type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,noresvport,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.152,mountvers=3,mountport=4002,mountproto=tcp,local_lock=all,addr=192.168.1.152)通過上面方法，可以對當前已經生成的NAS PV進行更新，並通過重啓Pod使其生效。（注意：noresvport參數生效有其特殊性，諮詢nas技術支持。）
升級Nas Controller：
上面的文檔只是把老版本生成的pv更新掛載參數，只有更新了nas controller版本後才能使後續生成的pv自動使用新掛載參數。
新Controller模板：
kind: Deployment
apiVersion: extensions/v1beta1
metadata:
name: alicloud-nas-controller
namespace: kube-system
spec:
strategy:
type: Recreate
template:
metadata:
labels:
app: alicloud-nas-controller
spec:
tolerations:
- operator: Exists
affinity:
nodeAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 1
preference:
matchExpressions:
- key: node-role.kubernetes.io/master
operator: Exists
priorityClassName: system-node-critical
serviceAccount: admin
hostNetwork: true
containers:
- name: nfs-provisioner
image: registry.cn-hangzhou.aliyuncs.com/acs/alicloud-nas-controller:v1.14.3.8-58bf821-aliyun
env:
- name: PROVISIONER_NAME
value: alicloud/nas
securityContext:
privileged: true
volumeMounts:
- mountPath: /var/log
name: log
volumes:
- hostPath:
path: /var/log
name: log通過下面命令重建Nas Controller：
# kubectl delete deploy alicloud-nas-controller
# kubectl create -f controller.yamlStorageClass更新：
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: alicloud-nas
mountOptions:
- nolock,tcp,noresvport
- vers=3
parameters:
server: "2564f49129-**.cn-shenzhen.nas.aliyuncs.com:/"
driver: nfs
provisioner: alicloud/nas
reclaimPolicy: Retain通過下面命令更新StorageClass：
# kubectl delete sc alicloud-nas
# kubectl create -f stroageclass.yaml驗證：
擴容應用Pod數量，生成新PVC、PV：
# kubectl get pv default-html-web-nas-5-pvc-91f37aa0-14f6-11ea-a9b7-00163e084110 -oyaml| grep mountOptions -A 6
mountOptions:
- nolock,tcp,noresvport
- vers=3
nfs:
path: /default-html-web-nas-5-pvc-91f37aa0-14f6-11ea-a9b7-00163e084110
server: 2564f49129-**.cn-shenzhen.nas.aliyuncs.com
persistentVolumeReclaimPolicy: Retain查看Pod掛載信息，noresvport等參數均已配置成功：
2564f49129-**.cn-shenzhen.nas.aliyuncs.com:/default-html-web-nas-5-pvc-91f37aa0-14f6-11ea-a9b7-00163e084110 on /var/lib/kubelet/pods/4bc4bb3e-14f7-11ea-a9b7-00163e084110/volumes/kubernetes.io~nfs/default-html-web-nas-5-pvc-91f37aa0-14f6-11ea-a9b7-00163e084110 type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,noresvport,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.1.152,mountvers=3,mountport=4002,mountproto=tcp,local_lock=all,addr=192.168.1.152)