Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`kmcp deploy` feedback

Aperta
#21 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
28/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
docker, go, helm, kubernetes

Direzione di ricerca

Inizia dai punti di ingresso dei comandi kmcp deploy, install e build e riproduci i comandi e gli errori mostrati nel report. Done dovrebbe coprire il namespace e il comportamento d’uso richiesti, indicazioni più chiare per l’installazione e il build, la gestione corretta delle immagini e le istruzioni per raggiungere un server distribuito.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

--namespace should default to the current context, not default.


When i run:

$ kmcp deploy -n mcp
🚀 Applying MCPServer to cluster...
error: resource mapping not found for name: "test" namespace: "mcp" from "/tmp/mcpserver-165274223.yaml": no matches for kind "MCPServer" in version "kagent.dev/v1alpha1"
ensure CRDs are installed first
Error: failed to apply to cluster: kubectl apply failed: exit status 1
Usage:
  kmcp deploy [flags]

Flags:
      --args strings         Command arguments

We should not print the usage here, and we should give a better error like "run kcmp install first"


When I try to install:

$ kmcp install
🚀 Deploying KMCP controller to cluster...
Error: invalid controller version: version cannot be empty
Usage:
  kmcp install [flags]

Flags:
  -h, --help                     help for install
      --namespace string         Namespace for the KMCP controller (defaults to kmcp-system) (default "kmcp-system")
      --registry-config string   Path to docker registry config file
      --version string           Version of the controller to deploy (defaults to kmcp version)

How do I know what version to use?

Since I don't know, I followed https://github.com/kagent-dev/kmcp/tree/main?tab=readme-ov-file#controller-installation. This doesn't work either...

$ kubectl apply -f https://raw.githubusercontent.com/kagent-dev/kmcp/main/config/default/ --dry-run
W0730 08:10:43.389988 3498929 helpers.go:703] --dry-run is deprecated and can be replaced with --dry-run=client.
error: unable to read URL "https://raw.githubusercontent.com/kagent-dev/kmcp/main/config/default/", server reported 400 Bad Request, status code=400

Helm doesn't work either:

$ helm repo add kmcp https://charts.kagent.dev
Error: looks like "https://charts.kagent.dev" is not a valid chart repository or cannot be reached: Get "https://charts.kagent.dev/index.yaml": dial tcp: lookup charts.kagent.dev: no such host

Finally I guess the version is v0.1.0 and kmcp install --version v0.1.0 worked


Now I can run kmcp deploy and it runs successfully. I get ImagePullBackOff trying to pull "test:latest". its also pulling howardjohn/agentgateway:1752179558 which is not great since its not the real release.

I think I need to build so I tried:

$ kmcp build --docker --tag localhost:5000/my-mcp:latest
Building Docker image for python project...
Error: docker build failed: exit status 1
Usage:
  kmcp build [flags]

Flags:
      --docker               Build Docker image
  -h, --help                 help for build
  -o, --output string        Output directory or image name
      --platform string      Target platform (e.g., linux/amd64,linux/arm64)
  -d, --project-dir string   Build directory (default: current directory)
  -t, --tag string           Docker image tag

Global Flags:
  -v, --verbose   verbose output

I have no clue what this means. Add -v makes it a bit more clear:

$ kmcp build --docker --tag localhost:5000/my-mcp:latest -v
Building MCP server in: /tmp/tmp.GthxiQesz6/test
Detected project file: pyproject.toml
Starting build process...
Detected project type: python
Building Docker image for python project...
Running: docker build -t test:localhost:5000/my-mcp:latest .
ERROR: failed to build: invalid tag "test:localhost:5000/my-mcp:latest": invalid reference format
Error closing pipe: close |0: file already closed

Finally figure out it should be --output which was not intuitive to me but works I guess. I ran kmcp build --docker --output localhost:5000/my-mcp -v and it works.

Now I do:

$ kmcp deploy -n mcp --image localhost:5000/my-mcp:latest
🚀 Applying MCPServer to cluster...
mcpserver.kagent.dev/test configured
✅ MCPServer 'test' applied successfully
💡 Check status with: kubectl get mcpserver test -n mcp
💡 View logs with: kubectl logs -l app.kubernetes.io/name=test -n mcp

Again it fails. I guess the build only built, it didn't push. I manually run docker push localhost:5000/my-mcp:latest and it works this time.

Now its deployed.. now what? How do I reach it? Where is it? I happened to know its on port 3000 but others may not

Lingua principale
Go
Stelle
476
Fork
69
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di kagent-dev/kmcp

Tutte le issue di kagent-dev/kmcp

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.