User “system:anonymous” cannot get path “/”

前端 未结 1 388
情歌与酒
情歌与酒 2021-01-04 07:59

I just setup a kubenetes cluster base on this link https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#multi-platform I check with kubectl get nodes, then t

相关标签:
1条回答
  • 2021-01-04 08:28

    The latest kubernetes deployment tools enable RBAC on the cluster. Jenkins is relegated to the catch-all user system:anonymous when it accesses https://192.168.70.94:6443/api/v1/.... This user has almost no privileges on kube-apiserver.

    The bottom-line is, Jenkins needs to authenticate with kube-apiserver - either with a bearer token or a client cert that's signed by the k8s cluster's CA key.

    Method 1. This is preferred if Jenkins is hosted in the k8s cluster:

    1. Create a ServiceAccount in k8s for the plugin
    2. Create an RBAC profile (ie. Role/RoleBinding or ClusterRole/ClusterRoleBinding) that's tied to the ServiceAccount
    3. Config the plugin to use the ServiceAccount's token when accessing the URL https://192.168.70.94:6443/api/v1/...

    Method 2. If Jenkins is hosted outside the k8s cluster, the steps above can still be used. The alternative is to:

    1. Create a client cert that's tied to the k8s cluster's CA. You have to find where the CA key is kept and use it to generate a client cert.
    2. Create an RBAC profile (ie. Role/RoleBinding or ClusterRole/ClusterRoleBinding) that's tied to the client cert
    3. Config the plugin to use the client cert when accessing the URL https://192.168.70.94:6443/api/v1/...

    Both methods work in any situation. I believe Method 1 will be simpler for you because you don't have to mess around with the CA key.

    0 讨论(0)
提交回复
热议问题