🐞 Bug Summary
When using the helm chart, the image versions are pinned to latest rater than the immutable tag created for this level. This will cause deployments to continuously upgrade internally.
This is typically handled by using appVersions which are pinned at specific chart releases
🧩 Affected Component
Select the area of the project impacted:
Helm deployments
🧩 Additional Context (optional)
Add any configuration details, flags, or related issues.
https://github.com/IBM/mcp-context-forge/blob/v1.0.0-RC-3/charts/mcp-stack/values.yaml#L88
https://github.com/IBM/mcp-context-forge/blob/v1.0.0-RC-3/charts/mcp-stack/values.yaml#L1005
(Although it may be best to implement the migration tag as part of a split from the mono repo approach as described in #1340)
🐞 Bug Summary
When using the helm chart, the image versions are pinned to
latestrater than the immutable tag created for this level. This will cause deployments to continuously upgrade internally.This is typically handled by using appVersions which are pinned at specific chart releases
🧩 Affected Component
Select the area of the project impacted:
mcpgateway- APImcpgateway- UI (admin panel)mcpgateway.wrapper- stdio wrapperHelm deployments
🧩 Additional Context (optional)
Add any configuration details, flags, or related issues.
https://github.com/IBM/mcp-context-forge/blob/v1.0.0-RC-3/charts/mcp-stack/values.yaml#L88
https://github.com/IBM/mcp-context-forge/blob/v1.0.0-RC-3/charts/mcp-stack/values.yaml#L1005
(Although it may be best to implement the migration tag as part of a split from the mono repo approach as described in #1340)