Zein Fahrozi

I really like to contribute to Argo Workflow but currently i don't know React. hehe

> This one's really simple even if you don't know much React if you want to give it a try 🙂 It is hacktoberfest after all! I think its time...

Yep have that problem too ``` Normal Scheduled 45m default-scheduler Successfully assigned airbyte/airbyte-cron-765ccb6b44-9lb2j to gke-ase1-glo-data-1-e2-std-14-36-de-s-3e48975c-4xw8 Warning FailedAttachVolume 45m attachdetach-controller Multi-Attach error for volume "pvc-cf321101-735f-47e1-ae5a-607a8c26fa1a" Volume is already used by pod(s)...

Is it related CSI Driver (GKE) here https://airbyte.gitbook.io/airbyte/deploying-airbyte/on-kubernetes#persistent-storage-on-gke-regional-cluster

Current work around ``` with Workflow( generate_name="test-", volumes=[ SecretVolume(name="service-account-credential",secret_name="service-account-credential") ], # We do this because of this bug https://github.com/argoproj-labs/hera/issues/835 volume_claim_templates=[ PersistentVolumeClaim( metadata=ObjectMeta(name="inWorkflow"), spec=PersistentVolumeClaimSpec( access_modes=["ReadWriteOnce"], resources=ResourceRequirements( requests={"storage": Quantity(__root__="1Gi")} ) ) )...

I encounter this bug also when trying to do this step https://www.talos.dev/v1.9/talos-guides/install/virtualized-platforms/proxmox/#qemu-guest-agent-support i can pull the image from docker but it cannot pull it when inside talos