Skip to content

[FAQ Bot] NEW: Why does my Kubernetes deployment work locally with kind but fail on Git #408

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
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[FAQ Bot] NEW: Why does my Kubernetes deployment work locally with kind but fail on Git #408

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
24 changes: 24 additions & 0 deletions ...deployment/004_1dad6c9bfa_kubernetes-kind-github-actions-control-plane-nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
id: 1dad6c9bfa
question: Why does my Kubernetes deployment work locally with kind but fail on GitHub
Actions with “could not locate any control plane nodes for cluster named 'agent-relay'”?
sort_order: 4
---

This usually happens because a GitHub-hosted runner starts from a clean environment and won’t have your local `kind` cluster already created. When your workflow tries to deploy to the `agent-relay` cluster, Kubernetes can’t find the control plane.

A fix is to ensure the `kind` cluster exists before you load Docker images or apply manifests. For example:

```bash
if ! kind get clusters | grep -qx "agent-relay"; then
kind create cluster --name agent-relay
fi
```

Then continue with the usual steps:
1. Load your Docker image into `kind`.
2. Apply your Kubernetes manifests.
3. Wait for the deployment rollout.
4. Verify the deployed API.

This won’t necessarily show up locally when testing with `act`, because your machine may already have a `kind` cluster named `agent-relay` from a previous run.