Skip to content

Conversation

@crivetimihai
Copy link
Member

Summary

This PR extracts the still-valid features from #1798 (now closed), which was superseded by existing implementations for external PostgreSQL and secret injection.

Changes:

  • Service annotations support: Adds mcpContextForge.service.annotations to allow LoadBalancer configuration (e.g., AWS NLB, GCP load balancer annotations)
  • CACHE_TYPE "none" option: Adds "none" as a valid cache type in the schema to allow disabling caching entirely

Why this matters:

  • Service annotations are essential for cloud deployments that require specific load balancer configurations
  • The "none" cache type allows deployments that don't need caching (e.g., single-node development environments)

Attribution

Original work by @jinzishuai in #1798 - thank you for identifying these gaps!

Files changed:

  • charts/mcp-stack/templates/service-mcp.yaml - Added annotations template block
  • charts/mcp-stack/values.schema.json - Added annotations schema and "none" to CACHE_TYPE enum
  • charts/mcp-stack/values.yaml - Added annotations default

Closes #1722 (partial - service annotations portion)

- Add mcpContextForge.service.annotations for LoadBalancer configuration
  (e.g., AWS NLB, GCP load balancer annotations)
- Add "none" as a valid CACHE_TYPE option in values.schema.json
  to allow disabling caching entirely

These changes were extracted from PR #1798, which was superseded by
existing implementations for external PostgreSQL and secret injection.

Co-authored-by: Mihai Criveti <crivetimihai@gmail.com>
Signed-off-by: Mihai Criveti <crivetimihai@gmail.com>
@crivetimihai crivetimihai merged commit 4f7af55 into main Jan 14, 2026
39 of 41 checks passed
@crivetimihai crivetimihai deleted the feat/helm-service-annotations-cache-none branch January 14, 2026 00:37
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.

[FEATURE][DB]: Support external database host/url

3 participants