Skip to content

[BUG]: Helm chart image version defaults are not pinned to the released version #4401

@lewis-relph

Description

@lewis-relph

🐞 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:

  • mcpgateway - API
  • mcpgateway - UI (admin panel)
  • mcpgateway.wrapper - stdio wrapper
  • Federation or Transports
  • CLI, Makefiles, or shell scripts
  • Container setup (Docker/Podman/Compose)
  • Other (explain below)

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageIssues / Features awaiting triage

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions