Re: [I] Unable to get the loadbalancer IP's in a CKS Cluster deployed in a VPC [cloudstack-kubernetes-provider]

["kiranchavala (via GitHub)" <gi...@apache.org>]

kiranchavala commented on issue #76:
URL: https://github.com/apache/cloudstack-kubernetes-provider/issues/76#issuecomment-3606421667

   Thanks @vishesh92  closing the issue after performing the workaround 
   
   ```
   There could be Calico routing edge case encountered in some environments. By default, Calico uses the 192.168.0.0/16 network for its pod IP pool when you install it with the standard manifests. To avoid potential routing conflicts with existing networks in your infrastructure, it’s advisable to customize the Calico IP pool to use a different subnet that doesn’t overlap with your current network setup.
   
   kubectl get ippool.crd.projectcalico.org -o yaml
   
   You can edit the IP pool to change the CIDR to a different subnet that fits your network architecture better. For example, you might choose to use 10.0.0.0/16.
   
   kubectl edit ippool default-ipv4-ippool
   
   and redeploy the pods
   
   kubectl delete pod –all -A
   
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org