problem description
create bootstrap role to give permission to connect apiserver request signature error, modified as follows:
[root@localhost kubeconfig]# kubectl create clusterrolebinding kubelet-bootstrap –clusterrole=system:node-bootstrapper –user=kubelet-bootstrap
Error from server (AlreadyExists): Clusterrolebindings, rbac authorization. K8s. IO “kubelet – the bootstrap” already exists p>
problem analysis
this is because an incorrect signature has been created previously, the signature is occupied, and the occupied signature
needs to be deletedproblem solved
1. Delete signature
kubectl delete clusterrolebindings kubelet-bootstrap
2, recreate successfully
[root@localhost kubeconfig]# kubectl create clusterrolebinding kubelet-bootstrap –clusterrole=system:node-bootstrapper –user=kubelet-bootstrap
clusterrolebinding.rbac.authorization.k8s.io/kubelet-bootstrap created
Read More:
- K8s deployment of single node Nacos error server is down now, please try again later
- How to Solve K8S Error getting node
- K8s error in installing calico plug-in
- K8s configure HTTPS with existing certificate
- Summary of k8s single master cluster deployment
- Common errors in k8s initialization_ [WARNING NumCPU]_ [WARNING SystemVerification]_ WARNING Hostname
- The deployment of etcd storage and flannel network configuration for kubernetes / k8s multi node deployment
- Installation of k8s Helm
- K8s deployment Kafka has been reporting errors.
- [CICD] Jenkins Role-based Authorization Strategy
- [Solved] kubelet Startup Error: cannot find network namespace for the terminated container
- for k, v in k_map: ValueError: too many values to unpack (expected 2)
- Location and optimization of server IO high problem
- How to solve SVN authorization failed error
- 【Error】gRPC failure=Status{code=UNAVAILABLE, description=io exception, cause=io.netty.channel.
- Realization of springboot authorization verification technology based on JWT
- Connection authorization failure occurred. Reason: local security service non retryable error solution
- VMware Workstation failed to start VMware Authorization Service
- solve!! VMware Workstation failed to start the VMware authorization service
- After CentOS 7 starts, the login box cannot be displayed. Press Alt + F2 to display “failed to start authorization manager”