[Improvement]: MCP Proxy Deployment to Gateway Fails due to Strict spec.version Validation

[YasiruDEX]

Please select the area the issue is related to

Area/LLM & MCP Governance (LLM providers, LLM proxy, MCP proxy, provider keys)

Please select the aspect the issue is related to

Aspect/LLM & MCP (LLM providers, LLM proxy, provider keys, MCP proxy)

Suggested Improvement

Currently, the UI allows users to enter any string for the version format. The system only catches the error at the backend during the deployment process, which completely halts the MCP proxy creation with a control plane error.

Error Log Snippet:

{"time":"2026-07-10T10:12:52.369539424Z","level":"ERROR","source":"/build/pkg/controlplane/client.go:2778","msg":"Failed to create MCP proxy from YAML","proxy_id":"9095bfbb-a410-40e6-88bf-2360e84e3ceb","error":"failed to deploy MCP proxy configuration from YAML: configuration validation failed with 1 error(s): 1. spec.version: Version must follow semantic versioning pattern (e.g., v1.0, v2.1.3)"}

Suggested Improvements

Instead of failing at the backend, we should prevent the user from making the mistake in the first place by enforcing the format at the UI level:

• Implement strict frontend regex validation (e.g., ^v\d+.\d+(.\d+)?$) on the version input box or YAML linter to provide real-time inline error feedback when an incorrect format is typed. To further enforce compliance and prevent failed deployments, the "Create" or "Deploy" button should remain disabled until the user enters a perfectly matched semantic version (e.g., v1.0, v2.1.3).

Related Issues

No response