Ask questions[SOLVED] Failed to apply the ServiceAccount needed for job execution: Post https://10.102.X.X:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings: Forbidden
Docker version: (
docker info preferred)
Docker version 18.03.1-ce, build 9ee9f40
Operating system and kernel: (
uname -r preferred)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Steps to Reproduce: Creating a new Custom cluster Results: New node stuck in provisioning
Answer questions ghost
Please re-open this issue. I tried the solution by @gioppoluca , teared down the cluster, cleaned the hosts, and tried to start it up again; still no success. My nodes are behind a corporate proxy as well.
FATA Failed to apply the ServiceAccount needed for job execution: Post https://HOSTNAME.CORP.DOMAIN:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?timeout=30s: Bad Gateway
my .docker/config.json has '*.CORP.DOMAIN' and the related subnet listed.