Christopher Adigun

Yes, VPP will take care of the dataplane packet processing, FRR will be where BGP will be running and controlling the routing-table of the VPP

Ok.. Reading through the slack archive, I am also using this in the context of Telco based architecture. If you need to discuss more about the approach/design let me know....

Can you shed more light on _**config selector at node level**_, I thought the config selection should be at the Pod level

Looks like the spiderpool-init also depends on the controller been up: ``` kubectl -n kube-system logs spiderpool-init {"level":"INFO","ts":"2024-02-07T00:27:31.072Z","logger":"Spiderpool-Init","caller":"cmd/config.go:211","msg":"Ignore creating default IPv4 Subnet or IPPool"} {"level":"INFO","ts":"2024-02-07T00:27:31.072Z","logger":"Spiderpool-Init","caller":"cmd/config.go:250","msg":"Ignore creating default IPv6 Subnet or...

Hi using the latest release, the above error is not occurring but stateful pods are not coming up, following is the error from kubectl describe pod: ``` QoS Class: BestEffort...

@cyclinder - I am currently using k0s and not kubeadm cluster, so **_kubectl get po -A -l component=kube-controller-manager_** and **_kubectl get cm -n kube-system kubeadm-config -o yaml_** will not work...

Works now after creating the configmap. For k0s, I am using the default settings, so the parameters can be retrieved from the k0s command **_k0s config create | grep -i...

**_kubectl get clusterconfig -o yaml_** does not work in the k0s: ``` ubuntu@k0s-spiderpool-test:~$ kubectl get clusterconfig -o yaml - clusterconfig error: the server doesn't have a resource type "clusterconfig" ```...

I think we can close issue for now, seems resolved from my side

@dougbtv - Please any idea when this will be done? This is affecting all k8s starting from 1.21 release