feat(applicationsets): deploy the agent plane (kagent + agentgateway) on EKS#21
Merged
Conversation
… on EKS The agent plane wasn't in the eks-gitops catalog, so on real EKS the operator's AgentFleet/ModelGateway reconcile had no kagent/agentgateway CRDs to target and stayed Pending. Add an addons-ai-platform ApplicationSet that installs, in sync-wave order, kagent-crds + agentgateway-crds (wave 40) then kagent + agentgateway (wave 42) — the same OCI charts and pinned versions kx runs (kagent 0.9.4, agentgateway 1.0.1), so EKS mirrors the locally verified install. No clusterName/vpcId parameters (upstream charts reject unknown values, as cert-manager did). Per-addon values files hold env deltas; the CRD charts are value-less.
CI Results
All validations passed. |
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.
The agent plane wasn't in the eks-gitops catalog, so on real EKS the operator's AgentFleet/ModelGateway reconcile had no kagent/agentgateway CRDs to target (stayed Pending). Adds an
addons-ai-platformApplicationSet installing kagent-crds + agentgateway-crds (wave 40) then kagent + agentgateway (wave 42) — same OCI charts + pinned versions kx runs (kagent 0.9.4, agentgateway 1.0.1). No clusterName/vpcId params (upstream charts reject them). Static-validated; mirrors the kx-verified install — live-verify on first EKS deploy.