Skip to content

Pin the MCP image to the public 0.2.1 release #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ravikiranvm merged 1 commit into from
Sep 22, 2026
Merged

Pin the MCP image to the public 0.2.1 release #40

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,7 +325,7 @@ External agents such as Claude Code or Codex connect to OpenOps through the `ope
Prerequisites:
- `global.publicUrl` must be `https://...` (plain `http` is only accepted for `localhost`), so enable TLS first.
- `OPS_OAUTH_RS_CLIENT_SECRET` must be declared under `openopsEnvSecrets` with a random value of at least 32 characters (`openssl rand -hex 32`). It is shared between the API and the MCP pod. When an external secret manager supplies the value, declare the key as `""`; with `externalSecrets.infraSecretName` set, the chart reads it from the infra secret (the Terraform-generated one on Azure), otherwise from the single remote secret. External Secrets fails the whole sync when a requested property is missing, which is why the chart does not declare this key by default.
- Pull access to the MCP image. Until the first public release the default `mcp.repository` is the private registry `openopsprivate.azurecr.io`; point `mcp.repository`/`mcp.tag` at an image your cluster can pull, or grant the cluster's node identity pull rights on that registry.
- The MCP image is pulled from the public registry (`openops.azurecr.io/openops-mcp`, pinned by `mcp.tag`), like Tables and Analytics; no pull credentials are needed. Point `mcp.repository`/`mcp.tag` elsewhere to run a different build.

Minimal override:
```yaml
Expand Down
7 changes: 2 additions & 5 deletions chart/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,11 +281,8 @@ mcp:
enabled: false
name: openops-mcp
image: openops-mcp
# Main-branch builds live in the private registry until the first public release; the
# public image will be openops.azurecr.io/openops-mcp:<version>. Pulling from the private
# registry needs pull access on the cluster (imagePullSecrets or a registry role).
repository: "openopsprivate.azurecr.io"
tag: "8e7c930f" # Independently versioned (8-char commit sha or release version), not global.version
repository: "openops.azurecr.io" # Always the public registry for mcp
tag: "0.2.1" # Independently versioned (openops-mcp release), not global.version
port: 3020
replicas: 2 # Stateless; any replica serves any request
resources:
Expand Down
Loading