polardb / polardb/polardbx-sql
关于文档中正式环境配置的k8s配置calico网络,controller一直not ready
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 337
- PR merge metrics
- No merged PRs in 30d
Description
官方文档中,使用k8s部署的calico使用的是3.15版本,但是根据calico的文档兼容k8s,1.21版本的需要calico 3.19以上版本。
然后使用3.15版本的calico配置文件controller一直停留在下面的日志:
2023-07-31 02:28:19.977 [WARNING][1] runconfig.go 154: unable to get KubeControllersConfiguration(default) error=connection is unauthorized: kubecontrollersconfigurations.crd.projectcalico.org "default" is forbidden: User "system:serviceaccount:kube-system:calico-kube-controllers" cannot get resource "kubecontrollersconfigurations" in API group "crd.projectcalico.org" at the cluster scope
2023-07-31 02:28:20.985 [WARNING][1] runconfig.go 154: unable to get KubeControllersConfiguration(default) error=connection is unauthorized: kubecontrollersconfigurations.crd.projectcalico.org "default" is forbidden: User "system:serviceaccount:kube-system:calico-kube-controllers" cannot get resource "kubecontrollersconfigurations" in API group "crd.projectcalico.org" at the cluster scope
然后我尝试使用不同的calico版本,包括3.16~3.19 都有问题(仅仅修改配置文件的镜像版本)
请问如何修正3.15版本中的当前的日志反馈的问题。
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the official production-environment Kubernetes deployment documentation and its Calico configuration, then compare the documented Calico 3.15 version with Kubernetes 1.21 compatibility requirements. Reproduce the calico-kube-controllers authorization error from the issue and verify the documented configuration leaves the controller ready. Done means the documentation and configuration no longer recommend an incompatible setup and the controller starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100