1

After a while I found out that I need to declare the container to have a privileged security context. Suddenly it works! spec: containers: - securityContext: privileged: true There is also an article showing how to have a two-layered setup where the container that hosts the actual application does not need to be privileged: https://itnext.io/...


1

If I have read this correctly you are trying to target different clusters with your provider so you can then use a helm_release. You need to have distinct providers for each cluster and differentiate them with an alias so. provider "helm" { kubernetes { host = "https://my_endpoint1" token = "provider.access_token1&...


1

I found a solution. The problem is actual for Kubernetes version 1.19+ and COS/Ubuntu images based on containerd for GKE nodes. Before the 1.19 version Kubernetes used to use Docker for building images, but now it uses containerd. More details could be found in the official Google Cloud documentation. You need to create and put an CA certificate to each GKE ...


1

If your on Standard Mode for your GKE cluster, go into Computer Engine > SSH into every node and put into /etc/docker/certs.d/<ip:port>/ca.cert. Create folder if it does not exists. This works for me. The method will not work for Autopilot Mode. My exact steps on each node: mkdir -p /etc/docker/certs.d/1.2.3.4:5000 cd /etc/docker/certs.d/1.2.3.4:...


1

Put it inside the sh? withKubeConfig(...) { sh “”” export ... kubectl ... “”” }


Only top voted, non community-wiki answers of a minimum length are eligible