Skip to content

Wait 120s after cluster is ACTIVE before connecting (awscli-cp-with-pcp) #599

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.

Sign up for GitHub

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

Open
ronaldngounou wants to merge 1 commit into
base: v2
Choose a base branch
from
Open

Wait 120s after cluster is ACTIVE before connecting (awscli-cp-with-pcp) #599

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions tests/tekton-resources/tasks/setup/eks/awscli-cp-with-pcp.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,11 @@ spec:
aws eks create-cluster --name $(params.cluster-name) --region $(params.region) --kubernetes-version $(params.kubernetes-version) --role-arn $SERVICE_ROLE_ARN --resources-vpc-config subnetIds=$subnets,securityGroupIds=$sg --control-plane-scaling-config tier=$(params.control-plane-tier) $ENDPOINT_FLAG
fi
aws eks $ENDPOINT_FLAG --region $(params.region) wait cluster-active --name $(params.cluster-name)
# Cluster is ACTIVE (create succeeded). Wait for the API server endpoint to
# become resolvable/discoverable before connecting with kubectl: the endpoint
# instances take time to come up and the Route53 record has a ~60s TTL, so
# connecting immediately can fail with "no such host".
sleep 120

@hakuna-matatah hakuna-matatah Aug 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

have you checked why wait won't internally wait until endpoint reachable ?

@ronaldngounou ronaldngounou Aug 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

aws eks wait cluster-active won't wait until the endpoint is reachable because the waiter model will only evaluate whether the cluster is active, failed, or deleting. It doesn't wait until the endpoint is reachable.

"ClusterActive": {
      "delay": 30,
      "operation": "DescribeCluster",
      "maxAttempts": 40,
      "acceptors": [
          { "state": "failure", "matcher": "path", "argument":
  "cluster.status", "expected": "DELETING" },
          { "state": "failure", "matcher": "path", "argument":
  "cluster.status", "expected": "FAILED"  },
          { "state": "success", "matcher": "path", "argument":
  "cluster.status", "expected": "ACTIVE"  }
      ]
  }

@hakuna-matatah hakuna-matatah Aug 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please ensure the check is - loop until it becomes active and break and/or 120sec if that's the SLO for r53 recs.

- name: write-kubeconfig
image: alpine/k8s:1.35.0
script: |
Expand Down