Skip to content

release v0.1.18#1

Merged
code-crusher merged 1 commit intomainfrom
v0.1.18
Sep 4, 2025
Merged

release v0.1.18#1
code-crusher merged 1 commit intomainfrom
v0.1.18

Conversation

@code-crusher
Copy link
Copy Markdown
Member

Description

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)

How Has This Been Tested?

  • Unit Tests
  • Integration Tests
  • Manual Testing

Screenshots (if applicable)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Related Issues

@matterai-app
Copy link
Copy Markdown

matterai-app Bot commented Sep 4, 2025

Code Quality new feature architecture

Description

This PR introduces the matterMCP component into the gravity-matter-enterprise Helm chart, while deprecating the standalone gravity-ci-cd-agent and gravity-matter charts. It updates chart versions and configures matterMCP with its own Kubernetes resources and dynamic API endpoint.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)

How Has This Been Tested?

  • Unit Tests
  • Integration Tests
  • Manual Testing

Screenshots (if applicable)

N/A

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Related Issues

N/A

Summary By MatterAI MatterAI logo

🔄 What Changed

This pull request deprecates the standalone gravity-ci-cd-agent and gravity-matter Helm charts by removing all their associated files. Concurrently, it integrates a new matterMCP component into the gravity-matter-enterprise Helm chart. This integration includes adding a new ConfigMap template, modifying deployment logic to dynamically set the MATTER_API_ENDPOINT for matterMCP to point to the matterBackend service, adding a new Ingress template, and updating the values.yaml with the matterMCP component's deployment, service, and ingress configurations. The gravity-matter-enterprise chart's appVersion, version, and maintainer email have also been updated.

🔍 Impact of the Change

This is a significant architectural refactoring that consolidates Matter AI components into a single enterprise Helm chart, simplifying deployment and management. It introduces a new matterMCP service with its own Kubernetes resources and external access capabilities. Users of the previously standalone gravity-ci-cd-agent and gravity-matter charts will need to migrate to the gravity-matter-enterprise chart. The dynamic configuration of MATTER_API_ENDPOINT enhances flexibility and maintainability for inter-service communication.

📁 Total Files Changed

  • charts/gravity-ci-cd-agent/Chart.yaml: Removed Helm chart metadata.
  • charts/gravity-ci-cd-agent/templates/_helpers.tpl: Removed common Helm labels template.
  • charts/gravity-ci-cd-agent/templates/deployments.yaml: Removed agent deployment definitions.
  • charts/gravity-ci-cd-agent/templates/pvc.yaml: Removed persistent volume claims definitions.
  • charts/gravity-ci-cd-agent/templates/rbac.yaml: Removed RBAC configurations (ServiceAccount, ClusterRole, ClusterRoleBinding).
  • charts/gravity-ci-cd-agent/templates/secrets.yaml: Removed secret definitions.
  • charts/gravity-ci-cd-agent/templates/services.yaml: Removed service definitions.
  • charts/gravity-ci-cd-agent/values.yaml: Removed default values for the agent.
  • charts/gravity-matter-enterprise/Chart.yaml: Updated chart versions (appVersion to 0.1.58, version to 0.1.18) and maintainer email.
  • charts/gravity-matter-enterprise/templates/configmap.yaml: Added matterMCP ConfigMap template.
  • charts/gravity-matter-enterprise/templates/deployments.yaml: Modified environment variable logic to dynamically set MATTER_API_ENDPOINT for matterMCP.
  • charts/gravity-matter-enterprise/templates/ingress.yaml: Added matterMCP Ingress template.
  • charts/gravity-matter-enterprise/values.yaml: Added matterMCP component configuration (deployment, service, ingress).
  • charts/gravity-matter/Chart.yaml: Removed Helm chart metadata.
  • charts/gravity-matter/templates/_helpers.tpl: Removed common Helm labels template.
  • charts/gravity-matter/templates/deployments.yaml: Removed agent deployment definitions.
  • charts/gravity-matter/templates/ingress.yaml: Removed ingress definitions.
  • charts/gravity-matter/templates/pvc.yaml: Removed persistent volume claims definitions.
  • charts/gravity-matter/templates/secrets.yaml: Removed secret definitions.
  • charts/gravity-matter/templates/services.yaml: Removed service definitions.
  • charts/gravity-matter/values.yaml: Removed default values for the agent.

🧪 Test Added

N/A

🔒Security Vulnerabilities

N/A

Tip

Quality Recommendations

  1. Provide a detailed migration guide for users of the deprecated gravity-ci-cd-agent and gravity-matter charts to the new gravity-matter-enterprise chart.

  2. Review and define appropriate liveness and readiness probes for the matterMCP deployment to ensure service stability and graceful restarts.

  3. Evaluate the default resource requests and limits for matterMCP in values.yaml to align with expected production workloads and prevent resource contention.

Tanka Poem ♫

Old charts now depart,
New MCP takes its place,
Enterprise unified.
Code flows, a new path unfolds,
Kubernetes, a fresh start. 🚀

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Helm as Helm Chart
    participant K8sAPI as Kubernetes API
    participant MCP as Matter AI MCP Service
    participant Backend as Matter AI Backend Service
    participant Ingress as Kubernetes Ingress
    participant Client as External Client

    Dev->>Helm: helm install/upgrade (gravity-matter-enterprise)
    Helm->>K8sAPI: Deploy ConfigMap (matter-ai-mcp-config)
    Helm->>K8sAPI: Deploy Deployment (matter-mcp-server)
    Helm->>K8sAPI: Deploy Service (matter-mcp-server-service)
    Helm->>K8sAPI: Deploy Ingress (matter-mcp-server-ingress)
    K8sAPI-->>Helm: Resources created
    Helm-->>Dev: Deployment successful

    activate MCP
    MCP->>K8sAPI: Read ConfigMap (matter-ai-mcp-config)
    Note over MCP: MATTER_API_ENDPOINT set to matterBackend service
    Client->>Ingress: HTTP/S Request (matterai-mcp.example.com)
    Ingress->>MCP: Route request
    MCP->>Backend: Call matterBackend API (http://matter-backend-service.namespace.svc.cluster.local:port)
    Backend-->>MCP: API Response
    MCP-->>Ingress: Response to client
    Ingress-->>Client: Response
    deactivate MCP
Loading

Copy link
Copy Markdown

@matterai-app matterai-app Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release v0.1.18 removes deprecated charts and adds new MCP component. Configuration and template improvements identified.

Skipped files
  • README.md: Skipped file pattern

Comment on lines 3 to +10
description: Helm chart to deploy Matter AI Code Review Backend for Enterprise
type: application
icon: https://matterai.dev/favicon.png
appVersion: 0.1.16
version: 0.1.17
appVersion: 0.1.58
version: 0.1.18
maintainers:
- name: Vatsal Bajpai
email: vatsal@matterai.dev
email: vatsal@matterai.so
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 Documentation Gap

Issue: Email domain changed from matterai.dev to matterai.so without updating description
Fix: Update description to reflect new domain or maintain consistency
Impact: Ensures documentation accuracy and brand consistency

Suggested change
description: Helm chart to deploy Matter AI Code Review Backend for Enterprise
type: application
icon: https://matterai.dev/favicon.png
appVersion: 0.1.16
version: 0.1.17
appVersion: 0.1.58
version: 0.1.18
maintainers:
- name: Vatsal Bajpai
email: vatsal@matterai.dev
email: vatsal@matterai.so
description: Helm chart to deploy Matter AI Code Review Backend for Enterprise
type: application
icon: https://matterai.so/favicon.png
appVersion: 0.1.58
version: 0.1.18
maintainers:
- name: Vatsal Bajpai
email: vatsal@matterai.so

Comment on lines +42 to 61
{{- range $key, $value := $component.deployment.env }}
- name: {{ $key }}
{{- if eq $key "MATTER_API_ENDPOINT" }}
{{- if eq $componentName "matterMCP" }}
value: "http://{{ $.Values.components.matterBackend.service.name }}.{{ $.Values.global.namespace }}.svc.cluster.local:{{ $.Values.components.matterBackend.service.port }}"
{{- else }}
{{- if kindIs "map" $value }}
{{- toYaml $value | nindent 14 }}
{{- else }}
value: {{ $value | quote }}
{{- end }}
{{- end }}
{{- else }}
{{- if kindIs "map" $value }}
{{- toYaml $value | nindent 14 }}
{{- else }}
value: {{ $value | quote }}
{{- end }}
{{- end }}
{{- end }}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Code Refactor

Issue: Complex nested conditional logic for MATTER_API_ENDPOINT makes template hard to read and maintain
Fix: Simplify the conditional structure and improve readability
Impact: Reduces template complexity and improves maintainability

Suggested change
{{- range $key, $value := $component.deployment.env }}
- name: {{ $key }}
{{- if eq $key "MATTER_API_ENDPOINT" }}
{{- if eq $componentName "matterMCP" }}
value: "http://{{ $.Values.components.matterBackend.service.name }}.{{ $.Values.global.namespace }}.svc.cluster.local:{{ $.Values.components.matterBackend.service.port }}"
{{- else }}
{{- if kindIs "map" $value }}
{{- toYaml $value | nindent 14 }}
{{- else }}
value: {{ $value | quote }}
{{- end }}
{{- end }}
{{- else }}
{{- if kindIs "map" $value }}
{{- toYaml $value | nindent 14 }}
{{- else }}
value: {{ $value | quote }}
{{- end }}
{{- end }}
{{- end }}
env:
{{- range $key, $value := $component.deployment.env }}
- name: {{ $key }}
{{- if and (eq $key "MATTER_API_ENDPOINT") (eq $componentName "matterMCP") }}
value: "http://{{ $.Values.components.matterBackend.service.name }}.{{ $.Values.global.namespace }}.svc.cluster.local:{{ $.Values.components.matterBackend.service.port }}"
{{- else if kindIs "map" $value }}
{{- toYaml $value | nindent 14 }}
{{- else }}
value: {{ $value | quote }}
{{- end }}
{{- end }}

Comment on lines +126 to +127
env:
MATTER_API_ENDPOINT: "example.com"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Code Refactor

Issue: Hardcoded example.com domain in MATTER_API_ENDPOINT environment variable
Fix: Use a more descriptive placeholder or template variable
Impact: Improves configuration clarity and reduces confusion during deployment

Suggested change
env:
MATTER_API_ENDPOINT: "example.com"
env:
MATTER_API_ENDPOINT: "http://matter-backend.example.com"

@code-crusher code-crusher merged commit f2bde39 into main Sep 4, 2025
1 check passed
@code-crusher
Copy link
Copy Markdown
Member Author

/matter release-notes

@matterai-app
Copy link
Copy Markdown

matterai-app Bot commented Sep 4, 2025

What's Changed

Summary

This release marks a significant architectural shift by deprecating the standalone gravity-ci-cd-agent and gravity-matter Helm charts. All related functionalities are now consolidated within the gravity-matter-enterprise chart, which has been updated to version 0.1.18 and introduces the new Matter AI MCP (Matter Control Plane) Server component.

New Features

  • Consolidated Helm Chart: The gravity-matter-enterprise Helm chart now serves as the single deployment point for Matter AI's backend and agent services, replacing the previously separate gravity-ci-cd-agent and gravity-matter charts.
  • Matter AI MCP Server: Introduced a new matterMCP component within the gravity-matter-enterprise chart, enabling the deployment of the Matter AI Control Plane Server. This component includes its own deployment, service, and configurable ingress.
  • Dynamic API Endpoint Configuration: The MATTER_API_ENDPOINT for the matterMCP server is now dynamically configured to point to the matterBackend service, ensuring seamless internal communication.

Bug fixes

Skip this section if none.

Commits

  • add MCP server for enterprise helm chart: Integrates the Matter AI MCP server component into the enterprise Helm chart, consolidating previous functionalities and updating chart versions. (cb3b19) by code-crusher(vatsal.bajpai05@gmail.com)

Dependencies added

  • Matter AI MCP Server Image (gravitycloud/matter-ai-mcp): A new container image dependency for the Matter AI Control Plane Server.
  • Internal Service Dependency on matterBackend: The matterMCP component now relies on the matterBackend service for its API communication, with its endpoint dynamically resolved within the cluster.

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