根据跟新后的6-7又做了一遍nginx-ingress-controller还是重启几次后就CrashLoopBackOff了
来源:6-7 实战Ingress控制器

扎西石
2021-12-15
根据跟新后的6-7又做了一遍,依然是执行 6-6-ingress-nginx-controller.yaml 这个yaml文件后还是发现pod一直在在试图重启。报错还是跟之前一样的:
E1214 12:22:35.857191 6 reflector.go:123] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:156: Failed to list *v1.Endpoints: endpoints is forbidden: User “system:serviceaccount:ingress-nginx:nginx-ingress-serviceaccount” cannot list resource “endpoints” in API group “” at the cluster scope
E1214 12:22:35.860909 6 reflector.go:123] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:155: Failed to list *v1.Secret: secrets is forbidden: User “system:serviceaccount:ingress-nginx:nginx-ingress-serviceaccount” cannot list resource “secrets” in API group “” at the cluster scope
E1214 12:22:35.862259 6 reflector.go:123] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:157: Failed to list *v1.Service: services is forbidden: User “system:serviceaccount:ingress-nginx:nginx-ingress-serviceaccount” cannot list resource “services” in API group “” at the cluster scope
E1214 12:22:35.863212 6 reflector.go:123] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:158: Failed to list *v1.ConfigMap: configmaps is forbidden: User “system:serviceaccount:ingress-nginx:nginx-ingress-serviceaccount” cannot list resource “configmaps” in API group “” at the cluster scope
E1214 12:22:35.863221 6 reflector.go:123] k8s.io/ingress-nginx/internal/ingress/controller/store/store.go:159: Failed to list *v1.Pod: pods is forbidden: User “system:serviceaccount:ingress-nginx:nginx-ingress-serviceaccount” cannot list resource “pods” in API group “” in the namespace “ingress-nginx”。因为ingress-controller起不来所以hello-world.info就取不到对应的address。个人感觉问题还是在ingress-nginx-controller这一层。虽图片描述然hello-world.info能ping通,但是80是没有起来的。
2回答
-
清风
2021-12-15
你进qq群,把几个yaml文件发出来看看
012023-03-31 -
清风
2021-12-15
root@local:~# vi cluster-role-binding.yaml apiVersion: rbac.authorization.k8s.io/v1beta1 kind: ClusterRoleBinding metadata: name: nginx-ingress-clusterrole-nisa-binding roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: nginx-ingress-clusterrole subjects: - kind: ServiceAccount name: nginx-ingress-serviceaccount namespace: ingress-nginx
参考这个赋予权限。另外你更新代码了吗
072023-04-01
相似问题