You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2022/09/09 11:01:53 UTC
[GitHub] [cloudstack] StepBee opened a new issue, #6723: Kubernetes Clusters cannot be deployed in VPCs
StepBee opened a new issue, #6723:
URL: https://github.com/apache/cloudstack/issues/6723
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
* Improvement Request
* Documentation Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Kubernetes Provider and VPC
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main branch.
-->
~~~
4.17.0.1
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
Advanced Networking
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Ubuntu based hosts using KVM Hypervisor
##### SUMMARY
<!-- Explain the problem/feature briefly -->
According to the documentation [Cloudstack Kubernetes Service](https://docs.cloudstack.apache.org/en/latest/plugins/cloudstack-kubernetes-service.html#kubernetes-clusters) a Kubernetes Cluster can be deployed in VPC Networks.
Unfortunately, creating a Kubernetes Cluster in a VPC (VPC enabled networks) is failing, because of the missing "Firewall Service" in all networks being VPC enabled.
Creating a NetworkOffering with VPC support does not allow to enable the "Firewall Service" via the provider VpcVirtualRouter, which makes sense, because VPC enabled network offerings use the "Network ACL Service".
Therefore i think either the documentation is not specific enough to exclude VPC, or the Kubernetes Service might require additional functionality to support VPC enabled networks and their "Network ACL Service" instead of the "Firewall Service".
Or i miss something obvious / misunderstand the documentation.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
- Create a VPC if not existing
- Create a Tier within the VPC if not existing, for example using the DefaultIsolatedNetworkOfferingForVpcNetworks Network Offering
- Try to create a Kubernetes Cluster selecting either the previously created VPC Tier network or any other VPC Tier network
~~~
Cloudstack will complain about the missing "Firewall Service" of the chosen network.
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Either the documentation should not mention the possibility to deploy Kubernetes Clusters in VPCs, or the Kubernetes Cluster Deployment should be able to handle "Network ACL Service" in addition the the currently supported "Firewall Service"
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Cloudstack will complain about the missing "Firewall Service" of the chosen network when trying to deploy a Kubernetes Cluster in any kind of VPC enabled network.
~~~
It would be great to see Kubernetes Clusters working in VPCs, because of the richer feature set the virtual router provides on VPCs, for example like easy possibility for Tiering / subnet separation and the possibility of Private Gateways with static routes.
--
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-unsubscribe@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rohityadavcloud closed issue #6723: Kubernetes Clusters cannot be deployed in VPCs
Posted by "rohityadavcloud (via GitHub)" <gi...@apache.org>.
rohityadavcloud closed issue #6723: Kubernetes Clusters cannot be deployed in VPCs
URL: https://github.com/apache/cloudstack/issues/6723
--
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-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] weizhouapache commented on issue #6723: Kubernetes Clusters cannot be deployed in VPCs
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on issue #6723:
URL: https://github.com/apache/cloudstack/issues/6723#issuecomment-1519009083
added to 4.18.1.0 milestone. cc @shwstppr
--
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-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rohityadavcloud commented on issue #6723: Kubernetes Clusters cannot be deployed in VPCs
Posted by "rohityadavcloud (via GitHub)" <gi...@apache.org>.
rohityadavcloud commented on issue #6723:
URL: https://github.com/apache/cloudstack/issues/6723#issuecomment-1571734476
Fixed in https://github.com/apache/cloudstack/pull/7479
--
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-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] tbendziula commented on issue #6723: Kubernetes Clusters cannot be deployed in VPCs
Posted by "tbendziula (via GitHub)" <gi...@apache.org>.
tbendziula commented on issue #6723:
URL: https://github.com/apache/cloudstack/issues/6723#issuecomment-1506608812
I would love to see this as a feature. Is there anything I could do to help here?
Anyway, is there a usable workaround for routing traffic between isolated networks (besides VPNs or using the public network)?
--
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-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] StepBee commented on issue #6723: Kubernetes Clusters cannot be deployed in VPCs
Posted by "StepBee (via GitHub)" <gi...@apache.org>.
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-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org