RANCHER-703 Investigate usage of AZ in rancher-vpc
AWS Resorces in folio-rancher-vpc
AZ | subnets |
|---|---|
us-west-2a | folio-rancher-vpc-public-us-west-2a |
us-west-2b | folio-rancher-vpc-public-us-west-2b |
us-west-2c | folio-rancher-vpc-public-us-west-2c |
us-west-2d | folio-rancher-vpc-public-us-west-2d |
Service | Name | Subnet |
|---|---|---|
Eks | folio-tmp | folio-rancher-vpc-private-us-west-2b |
Eks | folio-dev | folio-rancher-vpc-private-us-west-2b |
Eks | folio-perf | folio-rancher-vpc-private-us-west-2b |
Eks | folio-testing | folio-rancher-vpc-private-us-west-2b |
Eks | rancher | folio-rancher-vpc-private-us-west-2b |
rds | rds-folio-perf-folijet | folio-rancher-vpc-db-us-west-2a |
load-balancer application | k8s-cattlesy-rancher-00f9592647 | folio-rancher-vpc-public-us-west-2b |
load-balancer application | carrier-io-alb | folio-rancher-vpc-public-us-west-2b |
load-balancer application | jenkins-alb | folio-jenkins-vpc-public-us-west-2b |
load-balancer classic | a21c525fe51e14813839a231afc49e00 | folio-rancher-vpc-public-us-west-2a |
load-balancer network | k8s-bama-edgeconn-6a2fcb7a9e | folio-rancher-vpc-public-us-west-2a |
Volumes | a lot of volumes | one from these: us-west-2d, us-west-2c, us-west-2b, us-west-2a |
Open Search | es-folio-perf-folijet | folio-rancher-vpc-private-us-west-2a |
kafka | kafka-folio-perf-folijet | folio-rancher-vpc-private-us-west-2a |
Check if possible to reduce number of AZ's in use without resource recreation
In terraform code below we can filter the subnets that we want to use.
data "aws_subnets" "private" {
filter {
name = "vpc-id"
values = [data.aws_vpc.this.id]
}
filter {
name = "availability-zone"
values = ["us-west-2b","us-west-2a"]
}
tags = {
Type : "private"
}
}
If try to update already exist.
If deploy from zero.
Conclusion
We can't update our cluster without recreation. "You can't change which subnets Amazon EKS creates its network interfaces in after your cluster is created. " (source https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html )