Add E2E tests for all documented configuration options.
Users will deploy MCPServers with diverse configurations. We need confidence that all documented options work correctly in realistic scenarios, not just unit tests with mocked Kubernetes clients.
Tests should cover all storage types (ConfigMap mounting, Secret mounting with permission verification, EmptyDir volumes, and multiple mounts combined), port configurations (custom non-default ports, multiple MCPServers with same port in different namespaces), security contexts (runAsNonRoot enforcement, readOnlyRootFilesystem, default security context application), and custom metadata (custom labels/annotations, propagation to Deployment/Service, and updates without full recreation).
Add E2E tests for all documented configuration options.
Users will deploy MCPServers with diverse configurations. We need confidence that all documented options work correctly in realistic scenarios, not just unit tests with mocked Kubernetes clients.
Tests should cover all storage types (ConfigMap mounting, Secret mounting with permission verification, EmptyDir volumes, and multiple mounts combined), port configurations (custom non-default ports, multiple MCPServers with same port in different namespaces), security contexts (runAsNonRoot enforcement, readOnlyRootFilesystem, default security context application), and custom metadata (custom labels/annotations, propagation to Deployment/Service, and updates without full recreation).