Deployment Targets

Applies toSelf-Managed v2

1 min read

On this page

Endpoints
Specification
- Example
- Kubernetes

DeploymentTargets correspond to different Kubernetes namespaces in the same Kubernetes cluster that Ververica Platform runs in.

Once a DeploymentTarget resource is created, you can reference it in Deployment in application mode or SessionCluster resources. Note that a created DeploymentTarget is immutable.

The DeploymentTarget specification (.spec) is immutable, but updates to metadata are allowed.

Deleting a DeploymentTarget is only possible if it is not referenced by any Deployment or SessionCluster.

Endpoints

The following endpoints are available for interacting with DeploymentTargets:

URI	Method	Description
URI	Method	Description
/api/v1/namespaces/{namespace}/deployment-targets	GET	List all DeploymentTargets in the namespace
/api/v1/namespaces/{namespace}/deployment-targets	POST	Create the DeploymentTarget specified in the request body
/api/v1/namespaces/{namespace}/deployment-targets/{name}	GET	Get a DeploymentTarget by name
/api/v1/namespaces/{namespace}/deployment-targets/{name}	PUT	Upsert a DeploymentTarget by name
/api/v1/namespaces/{namespace}/deployment-targets/{name}	DELETE	Delete a DeploymentTarget by name

Specification

Example

YAML

1kind: DeploymentTarget
2apiVersion: v1
3metadata:
4  name: myDeploymentTarget
5  namespace: default
6  labels:
7    labelName: labelValue
8  annotations:
9    annotationName: annotationValue
10spec:
11  kubernetes:
12    namespace: staging

This is a required attribute that defines which Kubernetes namespace to use for Apache Flink® clusters referencing the DeploymentTarget. The spec.kubernetes.namespace field is an optional String. If not set, Ververica Platform will use the same Kubernetes namespace it is running in.

It is required that Ververica Platform's ServiceAccount has proper access rights that allow managing Apache 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.

Caution

It is recommended to run Ververica Platform and the Flink Jobs managed by Ververica Platform in separate Kubernetes namespaces.

Resource Labels

The Kubernetes resources created for a Deployment in application mode or SessionCluster will have the following Kubernetes resource labels.

Deployments (Application Mode)

Session Clusters

app

flink-job

system

ververica-platform

vvpNamespace

Namespace of the corresponding Deployment resource (metadata.namespace).

deploymentId

ID of the corresponding Deployment resource (metadata.id).

deploymentName

Name of the corresponding Deployment resource (metadata.name). The name will be reformatted to fulfill Kubernetes label value requirements, e.g. My Deployment Name will become my-deployment-name.

jobId

ID of the Job resource (metadata.id) that corresponds to the execution of the Deployment.

Was this helpful?

Yes No