Hi, While upgrading airbyte in our GKE we’re stumb...
# replication-troubleshooting
k
Hi, While upgrading airbyte in our GKE we’re stumbling across an issue where
airbyte-server
and
airbyte-cron
are both trying to mount
airbyte-volume-configs
workloads are on different nodes and are failing to both attach the volume
u
Were you able to hardcode the volume-configs to a specific node?
u
Had the same issue and were able to fix it by removing volume-configs: 1. commented out
- volume-configs.yaml
in the
kube/resources/kustomization.yaml
2. kubectl delete -f kube/resources/volume-configs.yaml 3. redeploy Airbyte 4. (Also had to manually delete pv and pvc, by patching
kubectl patch pv pvc-xxxx -p '{"metadata":{"finalizers":null}}'
)