Lu Chen
Lu Chen
Maybe I don't fully understand your question, let me try to answer it. 1. Adding new nodes to cluster involves the interaction between nodes and control plane. So basically the...
Please post the log of yurthub.
> > @twosson Sorry, I have checked the code of yurt-coordinator-ca-certs controller that use `yurt-coordinator-cert-controller` serviceaccount instead `yurt-manager`. > > https://github.com/openyurtio/openyurt/blob/734da95df42010d13b26625cc118dc59a2343a1f/pkg/yurtmanager/controller/yurtcoordinator/cert/yurt_coordinator_cert_controller.go#L201 > > > > Moreover, `Create secrets` rbac setting...
> Also, I have tried install with 1.5.0 version -- `helm upgrade --install yurt-manager -n kube-system openyurt/yurt-manager --version 1.5.0` The image of `yurt-manager` is still `openyurt/yurt-manager:v1.4.0`(Image ID: docker.io/openyurt/yurt-manager@sha256:12d4d9eb734164c7a3ece4aee9c59dce47ca91d786fbe8d34463b6872c88d2a0). > >...
@rambohe-ch @zyjhtangtang
/assign @luc99hen
@rambohe-ch @zyjhtangtang This fix can be tricky. Because currently all native resource informers are managed by `sharedInformerFactory` which maps one gvr to one informer. In this case, we need two...
There are other solutions though. 1. Create configmap informers directly without using sharedInformerFactory. This is simple but may be harmful to informer code management and readability. 2. Create separete RBAC...
The discussion above has gone a bit off track. Previously, the discussion was based on yurt-hub reusing the kubelet's certificate, and the apiserver restricting the way the kubelet accesses configmaps....