Failed to validate namespace existence: default about kubernetes-elastic-agents HOT 3 CLOSED

@JorritSalverda - for events and namespaces, the privileges must be cluster scoped. It should be a cluster role and a cluster role binding. Can you please try that out? Check https://github.com/kubernetes/charts/blob/master/stable/gocd/templates/gocd-ea-cluster-role.yaml and https://github.com/kubernetes/charts/blob/master/stable/gocd/templates/gocd-ea-cluster-role-binding.yaml for reference.

from kubernetes-elastic-agents.

Can you please clarify from which container you're copying the value for /var/run/secrets/kubernetes.io/serviceaccount/token ? And are you sure that the token matches the configured service account's token? You can match the values by doing

secret_name=$(kubectl get serviceaccount server --namespace=NAMESPACE  -o jsonpath="{.secrets[0].name}")
kubectl get secret $secret_name --namespace=NAMESPACE -o jsonpath="{.data['token']}" | base64 --decode

and

cat /var/run/secrets/kubernetes.io/serviceaccount/token inside the server container.

from kubernetes-elastic-agents.

Changing the Role and RoleBinding to ClusterRole and ClusterRoleBinding seemed to have helped. I also had to remove a % from the end of the /var/run/secrets/kubernetes.io/serviceaccount/token file content. When using kubectl describe secret TOKEN_NAME as described in the form it doesn't show this % at the end, so that's the better way to find the value.

Hopefully the setup for go.cd server running in Kubernetes can be simplified by implementing #44 for future users.

from kubernetes-elastic-agents.