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 folio-rancher-vpc-db-us-west-2a folio-rancher-vpc-private-us-west-2a |
us-west-2b | folio-rancher-vpc-public-us-west-2b folio-rancher-vpc-db-us-west-2b folio-rancher-vpc-private-us-west-2b |
us-west-2c | folio-rancher-vpc-public-us-west-2c folio-rancher-vpc-db-us-west-2c folio-rancher-vpc-private-us-west-2c |
us-west-2d | folio-rancher-vpc-public-us-west-2d folio-rancher-vpc-db-us-west-2d folio-rancher-vpc-private-us-west-2d |
Service | Name | Subnet |
---|---|---|
Eks | folio-tmp | folio-rancher-vpc-private-us-west-2b folio-rancher-vpc-private-us-west-2a folio-rancher-vpc-private-us-west-2c folio-rancher-vpc-private-us-west-2d |
Eks | folio-dev | folio-rancher-vpc-private-us-west-2b folio-rancher-vpc-private-us-west-2a folio-rancher-vpc-private-us-west-2c folio-rancher-vpc-private-us-west-2d |
Eks | folio-perf | folio-rancher-vpc-private-us-west-2b folio-rancher-vpc-private-us-west-2a folio-rancher-vpc-private-us-west-2c folio-rancher-vpc-private-us-west-2d |
Eks | folio-testing | folio-rancher-vpc-private-us-west-2b folio-rancher-vpc-private-us-west-2a folio-rancher-vpc-private-us-west-2c folio-rancher-vpc-private-us-west-2d |
Eks | rancher | folio-rancher-vpc-private-us-west-2b folio-rancher-vpc-private-us-west-2a folio-rancher-vpc-private-us-west-2c folio-rancher-vpc-private-us-west-2d |
rds | rds-folio-perf-folijet | folio-rancher-vpc-db-us-west-2a folio-rancher-vpc-db-us-west-2b folio-rancher-vpc-db-us-west-2c folio-rancher-vpc-db-us-west-2d |
load-balancer application | k8s-cattlesy-rancher-00f9592647 k8s-folioperf-6a8cf55ef4 k8s-foliodev-261073ab68 k8s-foliodevtamu-aa8b610ef7 k8s-kdtest-edgecaia-25f5239401 k8s-foliodevfolijetlo-6de6cc84ef k8s-kubecost-kubecost-4b7d59f069 k8s-foliodevcoreplatf-beaec623fe k8s-foliodevspanish-5bff201436 k8s-foliodevvolaris-aa16e3da99 k8s-foliodevvolaris2n-22a01b74b9 k8s-foliotesting-a482f0e192 k8s-foliotmp-6805b6fdcc k8s-foliodevthunderje-428ae326e7 k8s-foliodevfolijet-47ce37cdd9 k8s-foliotestingsprin-4d035c4caa k8s-folioperffolijet-e2dc6d1c05 k8s-foliodevvega-b76831ac94 k8s-foliodevspitfire-11afcc5f7c k8s-foliotestingtmp-3581d3236b k8s-foliodevnla-4486d438ed k8s-foliodevbama-ae2b096a25 k8s-foliodevfirebird-b89c43de00 k8s-foliotestingcypre-8ce486e2b4 k8s-foliotestingkarat-61307110f4 | folio-rancher-vpc-public-us-west-2b folio-rancher-vpc-public-us-west-2a folio-rancher-vpc-public-us-west-2c folio-rancher-vpc-public-us-west-2d |
load-balancer application | carrier-io-alb | folio-rancher-vpc-public-us-west-2b folio-rancher-vpc-public-us-west-2c |
load-balancer application | jenkins-alb | folio-jenkins-vpc-public-us-west-2b folio-jenkins-vpc-public-us-west-2a |
load-balancer classic | a21c525fe51e14813839a231afc49e00 a871f3879ea8041fb9a1f74aeb535f73 a07056ef5cb6f4eb9995fd611ff6faa4 a34930fc4b64e439f955a00a4da4d1f7 a279f82f0d261454c85166dc044d760b a6f9ae12131524c9b81250a9bd4e53ba a4a497d16d06d46f7b02a2058d6945a7 a790d0bf91b7b4518b9bebd6759943fd a0074d06e644465fbcbf4aaa4745d02 | folio-rancher-vpc-public-us-west-2a folio-rancher-vpc-public-us-west-2b folio-rancher-vpc-public-us-west-2c folio-rancher-vpc-public-us-west-2d |
load-balancer network | k8s-bama-edgeconn-6a2fcb7a9e k8s-firebird-edgesip2-6c768f9573 k8s-bama-edgesip2-bb4045b87b k8s-folijetl-edgesip2-730d7b0c20 k8s-thunderj-edgesip2-13fc882d72 k8s-spanish-edgesip2-039ee96dbd k8s-folijet-edgesip2-5fbdc5fa33 k8s-karate-edgeconn-675d3e9448 k8s-nla-edgeconn-8096178c80 k8s-sprint-edgesip2-65ce2392d5 k8s-spitfire-edgesip2-86ebc235c5 k8s-folijet-edgeconn-6ec7b98d35 k8s-sprint-edgeconn-96178787e4 k8s-vega-edgeconn-550338c52a k8s-volaris-edgeconn-082c58227f k8s-spitfire-edgeconn-2134cdefd5 k8s-folijet-edgeconn-f6b67decbc k8s-firebird-edgeconn-c6949acf30 k8s-karate-edgesip2-2d5fe57a2f k8s-coreplat-edgesip2-1eb967b719 k8s-volaris-edgesip2-a4309aa9c5 k8s-cypress-edgesip2-cf2de7ecaf k8s-nla-edgesip2-87da2dc4c8 k8s-thunderj-edgeconn-5846aec6a1 k8s-vega-edgesip2-426c512c30 k8s-cypress-edgeconn-a4272119fd k8s-folijet-edgesip2-3051ecc80a | folio-rancher-vpc-public-us-west-2a folio-rancher-vpc-public-us-west-2b folio-rancher-vpc-public-us-west-2c folio-rancher-vpc-public-us-west-2d |
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 folio-rancher-vpc-private-us-west-2b |
kafka | kafka-folio-perf-folijet | folio-rancher-vpc-private-us-west-2a folio-rancher-vpc-private-us-west-2b |
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 )