Skip to content

Support creating cluster in existing AWS VPC #1759

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

Merged
merged 18 commits into from
Jan 5, 2021
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update docs
  • Loading branch information
deliahu committed Jan 4, 2021
commit a22c1df88fc25146bd36336a977e00a3d573fa36
10 changes: 10 additions & 0 deletions docs/clusters/aws/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,16 @@ api_load_balancer_scheme: internet-facing
# note: if using "internal", you must configure VPC Peering to connect your CLI to your cluster operator
operator_load_balancer_scheme: internet-facing

# list of existing subnets in an existing VPC in which to create the Cortex cluster
# at least two subnets must be provided, and subnet_visibility (specified above) must be set accordingly
# this is an advanced feature and requires additional VPC configuration; see https://eksctl.io/usage/vpc-networking/#use-existing-vpc-other-custom-configuration
# here is an example:
# subnets:
# - availability_zone: us-west-2a
# subnet_id: subnet-060f3961c876872ae
# - availability_zone: us-west-2b
# subnet_id: subnet-0faed05adf6042ab7

# API Gateway [public (API Gateway will be used by default, can be disabled per API) | none (API Gateway will be disabled for all APIs)]
api_gateway: public

Expand Down