DataTalksClub / DataTalksClub/faq
[FAQ]
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 19
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 9
Description
Course
ai-dev-tools-zoomcamp
Question
Why does my Kubernetes deployment work locally with act but fail on GitHub Actions with "could not locate any control plane nodes for cluster named 'agent-relay'"?
Answer
A GitHub-hosted runner starts with a fresh environment and does not contain the local kind cluster that may already exist on your development machine.
This can cause the workflow to fail with:
ERROR: could not locate any control plane nodes for cluster named 'agent-relay'.
Before loading the Docker image into kind or deploying the Kubernetes manifests, make sure the cluster exists.
For example:
if ! kind get clusters | grep -qx "agent-relay"; then
kind create cluster --name agent-relay
fi
After the cluster is created, the workflow can continue with:
- Loading the Docker image into kind.
- Applying the Kubernetes manifests.
- Waiting for the deployment rollout.
- Verifying the deployed API.
This issue may not appear when testing locally with act if a kind cluster named "agent-relay" already exists on the local machine.
Checklist
- I have searched existing FAQs and this question is not already answered
- The answer provides accurate, helpful information
- I have included any relevant code examples or links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing FAQ entries and contribution structure; the issue body provides the question, explanation, error message, and shell example. Add the FAQ content while matching the surrounding format, then verify that the Kubernetes and GitHub Actions terminology and code block render correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, kubernetes
- Domain
- ci-cd, devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100