fix(mesh): clarify kumactl usage with Konnect global CP - #6614
Open
ashman1984 wants to merge 3 commits into
Open
fix(mesh): clarify kumactl usage with Konnect global CP#6614ashman1984 wants to merge 3 commits into
ashman1984 wants to merge 3 commits into
Conversation
## Description Clarifies when to use `kumactl` and `kubectl` with a Konnect managed global CP and Kubernetes zone CPs. The current guidance says `kumactl` is read-only because the mesh is deployed on Kubernetes. That isn't correct for the setup described here, where the global CP is managed by Konnect and Kubernetes hosts the zone CP. `kumactl` is used to manage mesh resources on the Konnect global CP, while `kubectl` is used to manage Kubernetes resources in the zone cluster. This updates the shared `kumactl` guidance to make that distinction clear.
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
lmilan
requested changes
Aug 10, 2026
Co-authored-by: Lucie Milan <32450552+lmilan@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Clarifies when to use
kumactlandkubectlwith a Konnect managed global CP and Kubernetes zone CPs.The current guidance says
kumactlis read-only because the mesh is deployed on Kubernetes.That isn't correct for the setup described here, where the global CP is managed by Konnect and Kubernetes hosts the zone CP.
kumactlis used to manage mesh resources on the Konnect global CP, whilekubectlis used to manage Kubernetes resources in the zone cluster.This updates the shared
kumactlguidance to make that distinction clear.Preview Links
Checklist
This change aligns with the existing zone migration and zone federation guidance, where
kumactlis used to apply Mesh resources to the Konnect global CP, and with behaviour we've previously confirmed through Support.descriptionentry in frontmatter.