Skip to content

mcp-server Kubernetes port name is "mcp" instead of "mcp-server", inconsistent with other components #2021

@junhaoliao

Description

@junhaoliao

Bug

In the CLP Helm chart, every component's Kubernetes port name matches its component
name. For example:

  • api-server uses port name "api-server"
  • log-ingestor uses port name "log-ingestor"
  • webui uses port name "webui"
  • database uses port name "database"

However, the mcp-server component uses port name "mcp" instead of "mcp-server".

This inconsistency appears in both the Deployment template
(mcp-server-deployment.yaml, container port and health check probe) and the Service
template (mcp-server-service.yaml, targetPort).

The Kubernetes port name character limit is 15, and "mcp-server" is only 10
characters, so there is no technical reason for the shorter name.

Expected behavior: The port name should be "mcp-server" to match the naming
convention used by all other components.

CLP version

7fb76c3

Environment

N/A (Helm chart template issue)

Reproduction steps

  1. Open tools/deployment/package-helm/templates/mcp-server-deployment.yaml.
  2. Observe that the container port on line 60 is named "mcp" instead of "mcp-server".
  3. Observe that the health-check YAML anchor &mcp-server-health-check on line 81 references port: "mcp" instead of port: "mcp-server".
  4. Open tools/deployment/package-helm/templates/mcp-server-service.yaml.
  5. Observe that targetPort on line 16 is "mcp" instead of "mcp-server".
  6. Compare with other component templates (e.g., api-server-deployment.yaml,log-ingestor-deployment.yaml) where the port name matches the component name.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions