Skip to content

chore: bump mcp-kubernetes to v0.0.14 and azure-api-mcp to v0.0.7#380

Merged
feiskyer merged 1 commit into
mainfrom
chore/bump-mcp-kubernetes-azure-api-mcp
Jun 18, 2026
Merged

chore: bump mcp-kubernetes to v0.0.14 and azure-api-mcp to v0.0.7#380
feiskyer merged 1 commit into
mainfrom
chore/bump-mcp-kubernetes-azure-api-mcp

Conversation

@gossion

@gossion gossion commented Jun 18, 2026

Copy link
Copy Markdown
Member

Summary

  • Bump github.com/Azure/mcp-kubernetes from v0.0.13 to v0.0.14
  • Bump github.com/Azure/azure-api-mcp from v0.0.5 to v0.0.7
  • Pull in transitive updates: mcp-go v0.46.0 → v0.54.1, OpenTelemetry v1.42.0 → v1.44.0, gRPC v1.79.3 → v1.81.1, and assorted golang.org/x/* bumps

Notable behavior change

mcp-kubernetes v0.0.14 tightens namespace validation: when --allow-namespaces is configured, commands must specify an explicit -n/--namespace flag unless the command is namespace-exempt. Updated TestValidateCommand_Combined to pass -n default for the kubectl drain node1 admin case so the test reflects the new (stricter) upstream contract.

Test plan

  • go build ./...
  • go test ./... (all packages pass; pre-existing cmd/aks-mcp Docker test is unrelated to this change and depends on Docker Desktop WSL2 integration)

- github.com/Azure/mcp-kubernetes: v0.0.13 -> v0.0.14
- github.com/Azure/azure-api-mcp: v0.0.5 -> v0.0.7
- Update transitive deps (mcp-go, otel, grpc, golang.org/x/*)
- Adapt drain test to mcp-kubernetes v0.0.14's stricter namespace
  validation: when --allow-namespaces is configured, commands must
  specify an explicit -n flag unless namespace-exempt

@feiskyer feiskyer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@feiskyer feiskyer added this pull request to the merge queue Jun 18, 2026
Merged via the queue into main with commit c1313a3 Jun 18, 2026
9 checks passed
@feiskyer feiskyer deleted the chore/bump-mcp-kubernetes-azure-api-mcp branch June 18, 2026 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants