docs: add Fleet Kuadrant MCP Gateway installation guide - #367
Merged
Conversation
Validated end-to-end against a real OCP dev cluster (Gateway API v1.1.0, Red Hat OSSM ambient mode): CRDs, controller/broker, kube-mcp-server, and cluster registration, including the mandatory kubernaut.ai/managed label without which Fleet silently ignores a registered cluster's alerts and remediations. Links from 03-deploy.md as an optional next step.
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
1 participant
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.
Summary
docs/installation/04-fleet-mcp-gateway.md, a step-by-step guide for installing the Kuadrant MCP Gateway (CRDs, controller, broker) andkube-mcp-server, the cluster-side prerequisite forspec.fleet.mcpGatewayType: kuadrant.initialize->tools/listhandshake through the real external Route.kagenti/KuadrantMCPGatewayExtensionnaming collision (ReferenceGrantRequireddespite an existingReferenceGrant), hostname/listener mismatches, transient registration validation delay, a harmless Gateway API version-skew log line, MCP session handling, the OLMkuadrant-operatornaming collision, and -- flagged explicitly per user request -- the mandatorykubernaut.ai/managed: "true"label without whichKuadrantRegistrysilently excludes a cluster from Fleet, so its alerts/remediations are never routed.03-deploy.mdas an optional next step.No
kubernaut-operatorcode changes -- this only documents provisioning steps for an already-implemented feature (issues #201/#224/#229).Test plan
oc rollout statussucceeds for the controller, broker, andkube-mcp-serverDeploymentsMCPServerRegistrationreachesREADY=Truewith tools discoveredinitialize+tools/listhandshake through the real external Route returns the expected aggregated tool setkubernaut.ai/managedlabel is present on the live registration and documented as mandatory