Skip to content
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

Support EKS eksctl --vpc-cidr argument in jx create cluster eks #2267

Closed
nukepuppy opened this issue Nov 15, 2018 · 5 comments
Closed

Support EKS eksctl --vpc-cidr argument in jx create cluster eks #2267

nukepuppy opened this issue Nov 15, 2018 · 5 comments
Labels
area/aws area/create-cluster area/eks support for AWS EKS kind/enhancement An enhancement of an existing feature lifecycle/rotten

Comments

@nukepuppy
Copy link

Summary

Support --vpc-cidr when using jx create cluster eks
eksctl supports the --vpc-cidr flag when doing eksctl create cluster

May be as simple as another #1461

Kubernetes cluster

What kind of Kubernetes cluster are you using & how did you create it?
Combination of eksctl / kops / jx for different purposes.. until feature parity exists between them all.

Expected behavior

Ideal goal is build the cluster I want on the network I want.

This facilitates being able to create an enterprise network structure and allow for peering and other network layer enhancements that are too restricting on the default VPC CIDR ranges

Actual behavior

Does not support the --vpc-cidr flag yet

@rainmanh
Copy link

rainmanh commented Nov 22, 2018

eksctl also supports existing subnets.
Probably a similar approach would work

eksctl-io/eksctl#305

eksctl-io/eksctl#306

@ccojocar ccojocar added kind/enhancement An enhancement of an existing feature priority/backlog labels Jan 16, 2019
@jenkins-x-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@jenkins-x-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot
Copy link
Contributor

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/aws area/create-cluster area/eks support for AWS EKS kind/enhancement An enhancement of an existing feature lifecycle/rotten
Projects
None yet
Development

No branches or pull requests

5 participants