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
- Open
tools/deployment/package-helm/templates/mcp-server-deployment.yaml.
- Observe that the container port on line 60 is named
"mcp" instead of "mcp-server".
- Observe that the health-check YAML anchor
&mcp-server-health-check on line 81 references port: "mcp" instead of port: "mcp-server".
- Open
tools/deployment/package-helm/templates/mcp-server-service.yaml.
- Observe that
targetPort on line 16 is "mcp" instead of "mcp-server".
- Compare with other component templates (e.g.,
api-server-deployment.yaml,log-ingestor-deployment.yaml) where the port name matches the component name.
Bug
In the CLP Helm chart, every component's Kubernetes port name matches its component
name. For example:
api-serveruses port name"api-server"log-ingestoruses port name"log-ingestor"webuiuses port name"webui"databaseuses port name"database"However, the
mcp-servercomponent 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 Servicetemplate (
mcp-server-service.yaml,targetPort).The Kubernetes port name character limit is 15, and
"mcp-server"is only 10characters, so there is no technical reason for the shorter name.
Expected behavior: The port name should be
"mcp-server"to match the namingconvention used by all other components.
CLP version
7fb76c3
Environment
N/A (Helm chart template issue)
Reproduction steps
tools/deployment/package-helm/templates/mcp-server-deployment.yaml."mcp"instead of"mcp-server".&mcp-server-health-checkon line 81 referencesport: "mcp"instead ofport: "mcp-server".tools/deployment/package-helm/templates/mcp-server-service.yaml.targetPorton line 16 is"mcp"instead of"mcp-server".api-server-deployment.yaml,log-ingestor-deployment.yaml) where the port name matches the component name.