-
Notifications
You must be signed in to change notification settings - Fork 352
Open
Description
📋 Prerequisites
- I have searched the existing issues to avoid creating a duplicate
- By submitting this issue, you agree to follow our Code of Conduct
- I am using the latest version of the software
- I have tried to clear cache/cookies or used incognito mode (if ui-related)
- I can consistently reproduce this issue
🎯 Affected Service(s)
Not Sure
🚦 Impact/Severity
Minor inconvenience
🐛 Bug Description
Hi Kagent community and thank you very much for maintaining the project.
During helm installation, we noticed the following issues with helm:
- Some components do not respect global
registryvalue, as we are using AWS ECR pull through cache with ghcr.io, we tried to set the following but did not work:
querydoc.image.registry
kmcp.image.repository
kagent-tools.image.repository
- grafana-mcp does not support specifying the image repo name, for the same reason to use ECR pull through cache for docker. setting
grafana-mcp.image.registrydid not work - disabling default agents did not work, as we do not use cilium, we tried setting the following, but the agents are deployed:
agents.cilium-policy-agent.enabled: false
agents.cilium-manager-agent.enabled: false
agents.cilium-debug-agent.enabled: false
The command used is:
helm upgrade --install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
--namespace kagent \
--set providers.default=openAI \
--set providers.openAI.apiKey=$OPENAI_API_KEY \
--set providers.gemini.apiKey=$GEMINI_API_KEY \
-f values.yaml
🔄 Steps To Reproduce
Install with the following values:
helm upgrade --install kagent oci://ghcr.io/kagent-dev/kagent/helm/kagent \
--namespace kagent \
-f values.yaml
registry: "<random_account_id>.dkr.ecr.us-east-1.amazonaws.com/ghcr"
grafana-mcp.image.registry: "<random_account_id>.dkr.ecr.us-east-1.amazonaws.com/docker/mcp"
querydoc.image.registry: "<random_account_id>.dkr.ecr.us-east-1.amazonaws.com/ghcr"
kmcp.image.repository: "<random_account_id>.dkr.ecr.us-east-1.amazonaws.com/ghcr/kagent-dev/kmcp/controller"
kagent-tools.image.repository: "<random_account_id>.dkr.ecr.us-east-1.amazonaws.com/ghcr/kagent-dev/kagent/tools"
agents.cilium-policy-agent.enabled: false
agents.cilium-manager-agent.enabled: false
agents.cilium-debug-agent.enabled: false
🤔 Expected Behavior
- Global
registryshould work for all images unless overridden per component - Being able to disable some of the default agents
📱 Actual Behavior
No response
💻 Environment
- OS and version: macOS 26.1
- Kubectl version: v1.34.2
- Kubernetes version: v1.33.5-eks-3025e55
- Kubernetes provider: aws
- Helm version: version.BuildInfo{Version:"v4.0.1", GitCommit:"12500dd401faa7629f30ba5d5bff36287f3e94d3", GitTreeState:"clean", GoVersion:"go1.25.4", KubeClientVersion:"v1.34"}
🔧 CLI Bug Report
agent.yaml
mcpserver.yaml
modelconfig.yaml
remotemcpserver.yaml
secrets.txt
toolserver.yaml
versions.txt
🔍 Additional Context
No response
📋 Logs
📷 Screenshots
No response
🙋 Are you willing to contribute?
- I am willing to submit a PR to fix this issue
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Backlog