StepBee commented on issue #6723: URL: https://github.com/apache/cloudstack/issues/6723#issuecomment-1518994488
I kind of worked around it for now by creating a Network Service Offering based on the Default Isolated network offering but with the option to specify the vlan. The VLAN is known to all switches and routers outside of Cloudstack and i can do the specific routing outside of cloudstack, while still keeping VR functionality in direction to public and make use of the Kubernetes provider integration with the Virtual Router. To implement the static route(s) in direction to the other involved networks on the Kubernetes nodes i use a DaemonSet with privileged rights and host network. The pod deployed by the DaemonSet with host network is implementing the required routes on each Kubernetes node. Still i would really like to see the possibility to Kubernetes Clusters in VPC networks. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
