Apache Flink Deployments reference a Deployment Target, which corresponds to different Kubernetes namespaces in the same Kubernetes cluster, that Ververica Platform runs in.
Additionally, the DeploymentTarget resource can provide a patch set that is applied to all Deployment resources that reference it.
Once a DeploymentTarget resource is created, you can reference it in Deployment resources. Note that a created DeploymentTarget are immutable.
Deleting a DeploymentTarget is only possible if it is not referenced by any Deployment.
This is a required attribute that defines which Kubernetes namespace to use for Flink deployments. The
spec.kubernetes.namespace field is an optional String. If not set, Ververica Platform
will use the same Kubernetes namespace it is running in.
kind: DeploymentTarget spec: kubernetes: namespace: staging
It is required that Ververica Platform’s ServiceAccount has proper access rights that allow managing Flink clusters in other Kubernetes namespaces.
For convenience, you can create the necessary Kubernetes Roles and RoleBindings via the Helm charts using the rbac.additionalNamespaces value.
It is recommended to run Ververica Platform and the Flink Jobs managed by Ververica Platform in separate Kubernetes Namespaces.