Implement CZERTAINLY Kubernetes Operator

[3keyroman]

Background

The current deployment method of the CZERTAINLY platform relies on the Helm chart, which supports most configuration options but has grown increasingly complex. To address deployment limitations and improve flexibility, we propose implementing a CZERTAINLY Kubernetes Operator.

Key Benefits of the Kubernetes Operator

1. Improved Configuration Management

• Enable the use of external Secrets and ConfigMaps for configuration without losing the ability to trigger changes dynamically when configurations are updated.
• This limitation in Helm prevents us from fully supporting these resources today, but an Operator would provide better flexibility for administrators.

2. Separation of Core Resources and Connectors

• While connectors can currently be enabled or disabled via Helm, adding new connectors indefinitely as sub-charts is impractical due to Kubernetes' manifest size limit.
• An Operator would allow for modular management of connectors, enabling deployment and removal from the UI, improving scalability and maintainability.

3. Seamless and Automated Upgrades

• Managing complex upgrades, including database migrations and third-party system component upgrades (e.g., messaging and API gateway), is challenging with Helm alone.
• Certain upgrades require more control to prevent disruptions, and an Operator would allow for automated, transparent upgrades without user intervention.

4. Custom Resource Definitions (CRDs) for CZERTAINLY

• Introduce CRDs to categorize and manage CZERTAINLY components more effectively.
• Integrate CZERTAINLY-Cert-Manager-Issuer as part of the Operator, eliminating the need for a separate Helm chart installation.

5. Enhanced Deployment Reliability & Webhook Support

• The Operator-driven deployment will be more resilient and easier to maintain for administrators.
• Webhooks can be leveraged to integrate with other Kubernetes resources and automate configuration changes within the platform.
• This separation allows cluster administrators to manage Kubernetes infrastructure while platform administrators focus on CZERTAINLY.

6. Automated Scaling

• Enable automatic scaling of CZERTAINLY components based on workload demand, optimizing resource usage and performance.

The introduction of a CZERTAINLY Kubernetes Operator will enhance deployment flexibility, automate upgrades, streamline connector management, improve maintainability, and provide a foundation for future scalability. This approach aligns with best practices for managing modern cloud-native applications.