CloudNativer
CloudNativer
You can try the following two methods: (1) Set the parameter "--enable-ibgp=false", do not let kubernetes node directly establish BGP neighbors with each other. Let your kubernetes node only build...
> You can try the following two methods: > (1) Set the parameter "--enable-ibgp=false", do not let kubernetes node directly establish BGP neighbors with each other. Let your kubernetes node...
> > You can try the following two methods: > > (1) Set the parameter "--enable-ibgp=false", do not let kubernetes node directly establish BGP neighbors with each other. Let your...
> > > You can try the following two methods: > > > (1) Set the parameter "--enable-ibgp=false", do not let kubernetes node directly establish BGP neighbors with each other....
Each kubernetes cluster in our production environment has 4000 nodes, and the whole network is interconnected by BGP, which has been running stably for more than one year. There are...
> I think your changes are reasonable, we have the same network topology and also will suffer from the same problem. Yes, when I communicate with many R & D...
> Just to clarify there is nothing implicit about the kube-router design that one would see these challenges with routing pod network CIDR. Users have to carefully choose the knobs...
> Just to clarify there is nothing implicit about the kube-router design that one would see these challenges with routing pod network CIDR. Users have to carefully choose the knobs...
> > If you set "--advertide-cluster-ip=false", our kubernetes service will not be able to route out. > > @cloudnativer Have you tried `kube-router.io/service.advertise.clusterip`? ----------------------------------------------------------------------------------------- [requirements and test instructions] Suppose we...
Please note that I've changed "advertise-cluster-subnet" to "advertise-service-cluster-ip-range". Keep the same parameter names as kube-api-server, kubeadm etc. Please see https://github.com/cloudnativelabs/kube-router/pull/920.