Update variables.tf bastion host instance type
Update EKS node instance with a tested workable instance type.
Test updates in my environment
Use Case
The same error as below occurs when I launch the Bastion host on it's own. When I change the instance type in variables.tf to m5n.xlarge it deploys the bastion host. So that default instance type should be changed as well.
Error: waiting for Auto Scaling Group (swf_ng-20230809230211731900000002) capacity satisfied: 1 error occurred:
│ * Scaling activity (d5a62772-25a3-3218-2623-e9ec177e0692): Failed: We currently do not have sufficient c4.8xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get c4.8xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2c. Launching EC2 instance failed.
│
│
│
│ with module.eks.module.aws_eks.module.self_managed_node_group["swf_ng"].aws_autoscaling_group.this[0],
│ on .terraform/modules/eks.aws_eks/modules/self-managed-node-group/main.tf line 412, in resource "aws_autoscaling_group" "this":
│ 412: resource "aws_autoscaling_group" "this" {
│
╵
╷
│ Error: waiting for EKS Add-On (ex-complete-508c:aws-ebs-csi-driver) create: timeout while waiting for state to become 'ACTIVE' (last state: 'DEGRADED', timeout: 20m0s)
│
│ with module.eks.module.eks_blueprints_kubernetes_addons.module.aws_ebs_csi_driver[0].aws_eks_addon.aws_ebs_csi_driver[0],
│ on .terraform/modules/eks.eks_blueprints_kubernetes_addons/modules/kubernetes-addons/aws-ebs-csi-driver/main.tf line 16, in resource "aws_eks_addon" "aws_ebs_csi_driver":
│ 16: resource "aws_eks_addon" "aws_ebs_csi_driver" {
│
╵
╷
│ Error: context deadline exceeded
│
│ with module.eks.module.eks_blueprints_kubernetes_addons.module.aws_efs_csi_driver[0].module.helm_addon.helm_release.addon[0],
│ on .terraform/modules/eks.eks_blueprints_kubernetes_addons/modules/kubernetes-addons/helm-addon/main.tf line 1, in resource "helm_release" "addon":
│ 1: resource "helm_release" "addon" {
Impact
We have a deadline very soon to have deployed Zarf infra to show customers.
Persona
IaC Wizard
Description
Update variables.tf bastion host instance type Update EKS node instance with a tested workable instance type. Test updates in my environment
Use Case
The same error as below occurs when I launch the Bastion host on it's own. When I change the instance type in variables.tf to m5n.xlarge it deploys the bastion host. So that default instance type should be changed as well.
Error: waiting for Auto Scaling Group (swf_ng-20230809230211731900000002) capacity satisfied: 1 error occurred: │ * Scaling activity (d5a62772-25a3-3218-2623-e9ec177e0692): Failed: We currently do not have sufficient c4.8xlarge capacity in the Availability Zone you requested (us-east-2b). Our system will be working on provisioning additional capacity. You can currently get c4.8xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-2a, us-east-2c. Launching EC2 instance failed. │ │ │ │ with module.eks.module.aws_eks.module.self_managed_node_group["swf_ng"].aws_autoscaling_group.this[0], │ on .terraform/modules/eks.aws_eks/modules/self-managed-node-group/main.tf line 412, in resource "aws_autoscaling_group" "this": │ 412: resource "aws_autoscaling_group" "this" { │ ╵ ╷ │ Error: waiting for EKS Add-On (ex-complete-508c:aws-ebs-csi-driver) create: timeout while waiting for state to become 'ACTIVE' (last state: 'DEGRADED', timeout: 20m0s) │ │ with module.eks.module.eks_blueprints_kubernetes_addons.module.aws_ebs_csi_driver[0].aws_eks_addon.aws_ebs_csi_driver[0], │ on .terraform/modules/eks.eks_blueprints_kubernetes_addons/modules/kubernetes-addons/aws-ebs-csi-driver/main.tf line 16, in resource "aws_eks_addon" "aws_ebs_csi_driver": │ 16: resource "aws_eks_addon" "aws_ebs_csi_driver" { │ ╵ ╷ │ Error: context deadline exceeded │ │ with module.eks.module.eks_blueprints_kubernetes_addons.module.aws_efs_csi_driver[0].module.helm_addon.helm_release.addon[0], │ on .terraform/modules/eks.eks_blueprints_kubernetes_addons/modules/kubernetes-addons/helm-addon/main.tf line 1, in resource "helm_release" "addon": │ 1: resource "helm_release" "addon" {
Impact
We have a deadline very soon to have deployed Zarf infra to show customers.
Completion