📋 Prerequisites
🎯 Affected Service(s)
Not Sure
🚦 Impact/Severity
No impact (Default)
🐛 Bug Description
When the kagent controller creates an Agent Pod, it resolves the image tag to a specific digest and writes that digest directly into the Pod spec. For example:
image: my-registry/app@sha256:e2d28...
At the time the Agent Pod was created, the tag 0.9.11 pointed to digest e2d28....
Later, I re-pushed the same image tag (0.9.11) to my private registry, and the tag now points to a new digest b024....
From my understanding, since the configuration is:
controller.agentDeployment.agentImage.tag=0.9.11
newly created Agent Pods should use whatever digest the tag 0.9.11 currently resolves to in the registry.
However, even after recreating Agent Pods and restarting the kagent controller, the generated Pod spec still references the old digest:
app@sha256:e2d28...
instead of the updated digest:
app@sha256:b024...
This suggests that kagent may be caching or persisting the initially resolved digest and continuing to reuse it, even after the tag has been updated in the registry.
As a result, the controller.agentDeployment.agentImage.tag setting does not appear to be effective once the digest has been resolved for the first time. Since the configuration specifies a tag rather than a digest, I would expect kagent to re-resolve the tag when creating new Agent Pods, or provide a mechanism to refresh the cached digest.
🔄 Steps To Reproduce
NA
🤔 Expected Behavior
No response
📱 Actual Behavior
No response
💻 Environment
No response
🔧 CLI Bug Report
No response
🔍 Additional Context
No response
📋 Logs
📷 Screenshots
No response
🙋 Are you willing to contribute?
📋 Prerequisites
🎯 Affected Service(s)
Not Sure
🚦 Impact/Severity
No impact (Default)
🐛 Bug Description
When the kagent controller creates an Agent Pod, it resolves the image tag to a specific digest and writes that digest directly into the Pod spec. For example:
image: my-registry/app@sha256:e2d28...
At the time the Agent Pod was created, the tag 0.9.11 pointed to digest e2d28....
Later, I re-pushed the same image tag (0.9.11) to my private registry, and the tag now points to a new digest b024....
From my understanding, since the configuration is:
controller.agentDeployment.agentImage.tag=0.9.11
newly created Agent Pods should use whatever digest the tag 0.9.11 currently resolves to in the registry.
However, even after recreating Agent Pods and restarting the kagent controller, the generated Pod spec still references the old digest:
app@sha256:e2d28...
instead of the updated digest:
app@sha256:b024...
This suggests that kagent may be caching or persisting the initially resolved digest and continuing to reuse it, even after the tag has been updated in the registry.
As a result, the controller.agentDeployment.agentImage.tag setting does not appear to be effective once the digest has been resolved for the first time. Since the configuration specifies a tag rather than a digest, I would expect kagent to re-resolve the tag when creating new Agent Pods, or provide a mechanism to refresh the cached digest.
🔄 Steps To Reproduce
NA
🤔 Expected Behavior
No response
📱 Actual Behavior
No response
💻 Environment
No response
🔧 CLI Bug Report
No response
🔍 Additional Context
No response
📋 Logs
📷 Screenshots
No response
🙋 Are you willing to contribute?