[Bug]:chaos Engineering resilience xercises fails to create alb and doesn't proceed to next steps #1728
Description
Installation method
Own AWS account
What happened?
The AWS Load Balancer Controller validating webhook is not ready.
The service aws-load-balancer-webhook-service has no endpoints.
Kubernetes rejects Ingress manifests and Terraform fails.
The fix is to wait for the controller to come up or restart the deployment
Waiting for application to become ready...
🔃 Cleaning up previous lab infrastructure...
🚧 Creating infrastructure for next lab...
╷
│ Error: API response status: Failure
│
│ with module.lab.kubernetes_manifest.ui_alb,
│ on lab/main.tf line 28, in resource "kubernetes_manifest" "ui_alb":
│ 28: resource "kubernetes_manifest" "ui_alb" {
│
│ Internal error occurred: failed calling webhook "vingress.elbv2.k8s.aws":
│ failed to call webhook: Post
│ "https://aws-load-balancer-webhook-service.kube-system.svc:443/validate-networking-v1-ingress?timeout=10s":
│ no endpoints available for service "aws-load-balancer-webhook-service"
╵
╷
│ Error: Kubernetes API Error: InternalError []
│
│ with module.lab.kubernetes_manifest.ui_alb,
│ on lab/main.tf line 28, in resource "kubernetes_manifest" "ui_alb":
│ 28: resource "kubernetes_manifest" "ui_alb" {
│
╵
╷
│ Error:
│
│ with module.lab.kubernetes_manifest.ui_alb,
│ on lab/main.tf line 28, in resource "kubernetes_manifest" "ui_alb":
│ 28: resource "kubernetes_manifest" "ui_alb" {
│
│ failed calling webhook "vingress.elbv2.k8s.aws": failed to call webhook:
│ Post
│ "https://aws-load-balancer-webhook-service.kube-system.svc:443/validate-networking-v1-ingress?timeout=10s":
│ no endpoints available for service "aws-load-balancer-webhook-service"
╵
🚨 An error occurred, please contact your workshop proctor or raise an issue at https://github.com/aws-samples/eks-workshop-v2/issues
The full log can be found here: /eks-workshop/logs/action-1765259340.log
What did you expect to happen?
We want the ALB to be created and webhook to be ceate and proceed to next steps
How can we reproduce it?
Retry the AWS observability eks workshop under chaos engineering resilience
Anything else we need to know?
No response
EKS version
latest under eks version 1.33