Skip to content

Conversation

@ppippi-dev
Copy link

🐛 Bug Description

Helm template validation fails with schema error after PR #1313 merged:
Error: values don't meet the specifications of the schema(s) in the following chart(s): mcp-stack:
mcpContextForge: Additional property metrics is not allowed

🔍 Root Cause

PR #1313 (Prometheus Metrics Instrumentation - Feature #218) added the metrics configuration to values.yaml but did not update the corresponding JSON schema in values.schema.json.

✅ Solution

Add the missing metrics property definition to values.schema.json under mcpContextForge properties, including:

  • enabled: Boolean to toggle metrics collection (default: true)
  • port: Integer for metrics endpoint port (range: 1-65535, default: 8000)
  • serviceMonitor: Object for Prometheus Operator ServiceMonitor configuration
    • enabled: Boolean to enable ServiceMonitor creation (default: true)
  • customLabels: Object for custom metric labels (default: {})

🧪 Testing

Verified the fix by running Helm template validation:

helm template mcp-stack -n mcp-stack charts/mcp-stack
✅ Command now completes successfully without schema validation errors.
📚 Related
Fixes schema validation error introduced in PR #1313
Related to Feature #218 (Prometheus Metrics Instrumentation)

PR IBM#1313 added metrics configuration to values.yaml but did not update
values.schema.json, causing helm template validation to fail with:
'Additional property metrics is not allowed'

This commit adds the metrics property definition to the schema including:
- enabled: boolean to toggle metrics collection
- port: integer for metrics endpoint port
- serviceMonitor: object for Prometheus Operator integration
- customLabels: object for custom metric labels

Fixes schema validation error introduced in PR IBM#1313
Related to Feature IBM#218 (Prometheus Metrics Instrumentation)

Signed-off-by: ppippi-dev <[email protected]>
@ppippi-dev ppippi-dev force-pushed the fix/helm-schema-metrics branch from 4c22a10 to c82092d Compare November 3, 2025 12:38
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