You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have run into issues trying to access the k8s api when running jobs as containers in containerMode: dind. We have a workflow with a job running in a container thats needs access to the cluster in order to run. I have provided the kubeconfig through a github secret. We also mount the /var/run/secrets/kubernetes.io/serviceaccount folder to the job container so it can access the kube-api-access- secrets. This does not work though, the container is unable to access the cluster.
Is using thecontainerMode: dind to access the k8s api feasible? Should I be using containerMode: kubernetes?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi! I have run into issues trying to access the k8s api when running jobs as containers in
containerMode: dind
. We have a workflow with a job running in a container thats needs access to the cluster in order to run. I have provided the kubeconfig through a github secret. We also mount the /var/run/secrets/kubernetes.io/serviceaccount folder to the job container so it can access the kube-api-access- secrets. This does not work though, the container is unable to access the cluster.Is using the
containerMode: dind
to access the k8s api feasible? Should I be usingcontainerMode: kubernetes
?Beta Was this translation helpful? Give feedback.
All reactions