Recent kubernet deployment tools include RBAC in the cluster. When he accesses https://192.168.70.94:6443/api/v1/..., Jenkins is discarded to all users system:anonymous. This user has virtually no privileges for kube-apiserver.
The bottom line is that Jenkins must authenticate with kube-apiserver - either with a token-holder or with a client certificate signed by the k8s cluster CA key.
Method 1. This is preferable if Jenkins is hosted in a k8s cluster:
- Create a ServiceAccount in k8s for the plugin
- Create an RBAC profile (i.e. Role / RoleBinding or ClusterRole / ClusterRoleBinding) tied to ServiceAccount
- Configure the plugin to use the ServiceAccount token when accessing the URL
https://192.168.70.94:6443/api/v1/...
2. Jenkins k8s, . :
- , CA- k8s. , CA, .
- RBAC (.. Role/RoleBinding ClusterRole/ClusterRoleBinding),
- URL
https://192.168.70.94:6443/api/v1/...
. , 1 , CA.