- cert-manager Operator: Ensure that the
cert-manager
operator is pre-installed. For more details on setting this up, refer to the official guide.
- This chart is based on Flink Kubernetes Operator v1.9.0. You can find the release here.
- It's crucial to keep track of operator versions, as new releases may upgrade the Flink version or introduce additional CRDs that can help manage deployments more effectively.
Off flink CRD usage example
This section defines default values for common properties such as the Flink version and the Kubernetes service account. These default values are applicable across all Flink deployments, with the flexibility to override them based on your custom requirements.
Defines the properties for Session Mode Flink setup. Only one instance of Flink can be deployed in this mode. This setup does not include job definitions—it's focused solely on the server part.
This section depends on the Session Mode configuration. It can be expanded to leverage external Flink clusters without needing to deploy a separate cluster for each job.
Recommended for production environments, the applicationMode
section is designed as a list of jobs, each with its independent configuration. This mode offers a more scalable approach for managing multiple Flink jobs within the same deployment.