Skip to content

feat: add pod extension points to the mcp-stack gateway (command, extra containers, volumes) - #6955

Open
healdropper wants to merge 1 commit into
IBM:mainfrom
healdropper:main
Open

healdropper wants to merge 1 commit into
IBM:mainfrom
healdropper:main

Conversation

@healdropper

Copy link
Copy Markdown

The mcp-stack gateway deployment currently offers no way to add sidecar containers, extra init containers, extra volumes/mounts, or to wrap the container entrypoint. Running the gateway against managed infrastructure often needs exactly that — e.g. a cloud-sql-proxy sidecar for an external Postgres, or an init container that materializes secrets from a CSI mount before the gateway starts.

This adds the standard optional extension values under mcpContextForge, all default-empty:

  • command / args: override the gateway container entrypoint
  • extraInitContainers / extraContainers
  • extraVolumes / extraVolumeMounts

Backwards compatible: with default values the rendered output is byte-identical to the current chart (helm template diff is empty). Verified with helm lint and a values file exercising every new field (init container, sidecar, entrypoint wrapper, volume + mount).

…ra containers, volumes)

The gateway deployment cannot currently host sidecars (e.g. a cloud-sql-proxy
for external Postgres), extra init containers (e.g. a secrets bootstrapper),
extra volumes/mounts, or an entrypoint wrapper. Add the standard optional
extension values, all default-empty:

- mcpContextForge.command / args: override the container entrypoint
- mcpContextForge.extraInitContainers / extraContainers
- mcpContextForge.extraVolumes / extraVolumeMounts

With default values the rendered output is byte-identical to the current
chart.

Signed-off-by: healdropper <1035382+healdropper@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant