shayktrust commented on issue #768:
URL:
https://github.com/apache/apisix-helm-chart/issues/768#issuecomment-2214582503
Hi @kworkbee ,
I am using Cluster Autoscaler, not Karpenter. Additionally, since I am
implementing high availability, I have configured etcd to mount to EFS using a
StorageClass. This setup ensures compatibility across all my availability zones.
```
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: efs-apisix
provisioner: efs.csi.aws.com
allowVolumeExpansion: true
parameters:
provisioningMode: efs-ap
fileSystemId: fs-xxxxxxxx
directoryPerms: "777"
gidRangeStart: "1000"
gidRangeEnd: "2000"
reclaimPolicy: Retain
mountOptions:
- tls
---
apiVersion: v1
kind: PersistentVolume
metadata:
name: efs-apisix
spec:
capacity:
storage: 10Gi
volumeMode: Filesystem
accessModes:
- ReadWriteMany
persistentVolumeReclaimPolicy: Retain
storageClassName: efs-apisix
csi:
driver: efs.csi.aws.com
volumeHandle: fs-xxxxxxxx
nodeAffinity:
required:
nodeSelectorTerms:
- matchExpressions:
- key: eks/nodeGroupSize
operator: In
values:
- BIG
- key: eks/efs
operator: In
values:
- indeed
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: efs-apisix-claim
spec:
accessModes:
- ReadWriteMany
storageClassName: efs-apisix
resources:
requests:
storage: 10Gi
```
using the following command temporarily resolved my issue:
```
kubectl delete pvc -l app.kubernetes.io/name=etcd -n <namespace>
kubectl delete statefulset apisix-etcd -n <namespace>
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
