E
E
ENigma3712021-10-19 17:59:20
Kubernetes
ENigma371, 2021-10-19 17:59:20

When creating Creating a ClusterRoleBinding, it comes out unchanged, what could be the problem?

Colleagues at this step

Creating a ClusterRoleBinding
In most cases after provisioning cluster using kops, kubeadm or any other popular tool, the ClusterRole cluster-admin already exists in the cluster. We can use it and create only ClusterRoleBinding for our ServiceAccount. If it does not exist then you need to create this role first and grant required privileges manually.

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: admin-user
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: admin-user
  namespace: kubernetes-dashboard

Issues
clusterrolebinding.rbac.authorization.k8s.io/admin-user unchanged
which prevents you from going to the next step to install kubernetes-dashboard.
Tell me what kind of error is not priority and fairness, request and how it can be solved I will be very grateful
kubectl get secret,sa,role,rolebinding,services,deployments --namespace=kubernetes-dashboard | grep dashboard
I1019 17:49:18.279265  855685 request.go:665] Waited for 1.149398152s due to client-side throttling, not priority and fairness, request: GET:https://10.70.40.76:6443/apis/certificates.k8s.io/v1?timeout=32s
I1019 17:49:28.678460  855685 request.go:665] Waited for 1.196920699s due to client-side throttling, not priority and fairness, request: GET:https://10.70.40.76:6443/apis/events.k8s.io/v1beta1?timeout=32s
I1019 17:49:38.682127  855685 request.go:665] Waited for 1.197929624s due to client-side throttling, not priority and fairness, request: GET:https://10.70.40.76:6443/apis/events.k8s.io/v1beta1?timeout=32s
I1019 17:49:48.881991  855685 request.go:665] Waited for 5.397901949s due to client-side throttling, not priority and fairness, request: GET:https://10.70.40.76:6443/apis/autoscaling/v2beta1?timeout=32s

Answer the question

In order to leave comments, you need to log in

1 answer(s)
D
Dmitry Shitskov, 2021-10-19
@Zarom

unchanged - means that the applied manifest already corresponds to the current state. Those. ClusterRoleBinding has been created.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question