Support "jx create cluster eks" using existing VPC and subnets

[mailjunze]

Summary

jx create cluster eks doesnt allow to choose existing subnets

Steps to reproduce the behavior

Expected behavior

jx create cluster eks --subnets <subnet1,subnet2>

eksctl provides supports for VPC/Subnets|

eksctl create cluster
--vpc-private-subnets=subnet-0ff156e0c4a6d300c,subnet-0426fb4a607393184
--vpc-public-subnets=subnet-0153e560b3129a696,subnet-009fa0199ec203c37

Actual behavior

Jx version

The output of jx version is:
jx version ec2-user@ip-172-31-9-12
NAME VERSION
jx 1.3.1008
jenkins x platform 0.0.3588
Kubernetes cluster v1.11.8-eks-7c34c0
kubectl v1.11.5
helm client v2.13.1+g618447c
helm server v2.13.1+g618447c
git git version 2.17.2
Operating System Linux distribution Linux version 4.14.77-86.82.amzn2.x86_64 ) (gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC)) #1 SMP Mon Dec 3 19:40:13 UTC 2018

COPY OUTPUT HERE

Jenkins type

• Classic Jenkins
• Serverless Jenkins

Kubernetes cluster

Operating system / Environment

[sharepointoscar]

Right, jx create cluster eks does not have flags to pass existing VPC/subnets. What you can do, is create your cluster using other tools like eksctl or KOPS. Once it is created, you can set your kubectl context to said cluster, then execute the jx install.

[patrickleet]

@sharepointoscar was thinking of doing the above with EKS next time around to take advantage of their new declarative/gitops configs

[sharepointoscar]

@ccojocar if we implement this for EKS, would it make sense to also implement for Azure and GCP to also allow folks to install on specific networks?

[jenkins-x-bot]

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]

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

[deanesmith]

/area jenkins

[jenkins-x-bot]

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]

@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.