-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws-eks): add service ip range setting to cluster class #16541
Comments
That's right. But even if the property is not exposed by the high-level construct ( |
I had a brief look as source code and correct me if I'm wrong, but I't seems to me that I might create a PR for this issue, but testing is a bit of an challenge. Let's say I would like to do some manual tests. How can I install local version of |
Yes, take a look at our contributing guide. In particular, there is a |
Refs: 1. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-eks-cluster-kubernetesnetworkconfig.html 2. https://docs.aws.amazon.com/eks/latest/APIReference/API_KubernetesNetworkConfigRequest.html#AmazonEKS-Type-KubernetesNetworkConfigRequest-serviceIpv4Cidr Notes: 1. Currently I have not updated the integ tests since the deployed takes a lot of time and it requires inferentia service limit increase. Do you think this change needs an integ tests updating (tried it out locally and it succeeded till auto-scaling)? 2. Couldn't find a good place in the Readme to add this feature. Would really help if we could come up with a good explanation and place for the same. Closes #16541 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Refs: 1. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-eks-cluster-kubernetesnetworkconfig.html 2. https://docs.aws.amazon.com/eks/latest/APIReference/API_KubernetesNetworkConfigRequest.html#AmazonEKS-Type-KubernetesNetworkConfigRequest-serviceIpv4Cidr Notes: 1. Currently I have not updated the integ tests since the deployed takes a lot of time and it requires inferentia service limit increase. Do you think this change needs an integ tests updating (tried it out locally and it succeeded till auto-scaling)? 2. Couldn't find a good place in the Readme to add this feature. Would really help if we could come up with a good explanation and place for the same. Closes aws#16541 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
In console we can specify Service IPv4 range, same goes with
CfnCluster
class, which containskubernetesNetworkConfig?
property. Unfortunately it is not possible to set it viaCluster
class.Use Case
We planed to migrate our on-premis k8s kluster to aws. To do it we planned to expose pod's k8s network and service k8s network to EKS via VPN and adjust CoreDNS accordingly. Unfortunately by default k8s comes with service ip range of 10.96.0.0/12, EKS comes with 10.100.0.0/16, which overlap. Since our cluster is up and running, we cannot change it. The only option to enable this scenerio is to create new EKS cluster with different service ip range.
Proposed Solution
Actually I'm not sure how
Cluster
class works ATM, but if it usesCfnCluster
class underneath, it is only a matter of exposingkubernetesNetworkConfig?
property.This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: