# 2021-07-12-18:45:10+0800 upgrade tiflash node

- Cause:
SES wants their tiflash run on vm which has 32c 
- Operation:
1. KUBECONFIG=9c68b3fe kubectl -n tidb1379661944580554066 get pvc data0-db-tiflash-0 -o yaml > tiflash-pvc.yaml
2. KUBECONFIG=9c68b3fe kubectl -n tidb1379661944580554066 edit pvc data0-db-tiflash-0 
3. set the pvc size to 1024Gi
4. wait the pv size is extended to 1024Gi 
5. kubectl -n garden-prod get shoot 9c68b3fe -o yaml > 9c68b3fe.old 
6. kubectl -n garden-prod edit shoot 9c68b3fe
7. add ```
    - annotations:
        pingcap.com/gcp-local-volume-count: "0"
        pingcap.com/gcp-provider-annotation: "true"
      labels:
        gardener.node.az.info: us-west1-a
        gardener.node.machine.type: n2-standard-32
        gardener.wg.name: tidb1379661944580554066-tiflash-a
        gardener.wg.prefix.name: tidb1379661944580554066-tiflash
        tenant: "1311274104996761600"
        tidbcluster: tidb1379661944580554066
      machine:
        image:
          name: centos-tidb-v20210420
          version: 7.8.2003
        type: n2-standard-32
      maxSurge: 1
      maxUnavailable: 0
      maximum: 1
      minimum: 1
      name: 26dc5157
      taints:
      - effect: NoSchedule
        key: dedicated
        value: tidb-tiflash
      volume:
        size: 50Gi
        type: pd-standard
      zones:
      - us-west1-a
```
- Impact:
the tiflash will running on n2-standard-32 which contains 32c
- Recovery operation:
KUBECONFIG=9c68b3fe kubectl apply -f tiflash-pvc.yaml
kubectl -n garden-prod apply -f 9c68b3fe.old
- Time window:
[2021-07-12:18:55:00 - 2021-07-12:19:20:00]