Коллеги при выполнении данного шага
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
Выдает
clusterrolebinding.rbac.authorization.k8s.io/admin-user unchanged
что не дает перейти к след шагу по установке kubernetes-dashboard.
Подскажите что за ошибка not priority and fairness, request и как ее можно решить буду оч благодарен
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
Простой
