This page describes how to deploy a Flink session cluster natively on Kubernetes.
~/.kube/config. You can verify permissions by running
kubectl auth can-i <list|create|edit|delete> pods.
Follow these instructions to start a Flink Session within your Kubernetes cluster.
A session will start all required Flink services (JobManager and TaskManagers) so that you can submit programs to the cluster. Note that you can run multiple programs per session.
All the Kubernetes configuration options can be found in our configuration guide.
Example: Issue the following command to start a session cluster with 4 GB of memory and 2 CPUs with 4 slots per TaskManager:
In this example we override the
resourcemanager.taskmanager-timeout setting to make
the pods with task managers remain for a longer period than the default of 30 seconds.
Although this setting may cause more cloud cost it has the effect that starting new jobs is in some scenarios
faster and during development you have more time to inspect the logfiles of your job.
The system will use the configuration in
Please follow our configuration guide if you want to change something.
If you do not specify a particular name for your session by
kubernetes.cluster-id, the Flink client will generate a UUID name.
Use the following command to submit a Flink Job to the Kubernetes cluster.
There are several ways to expose a Service onto an external (outside of your cluster) IP address.
This can be configured using
ClusterIP: Exposes the service on a cluster-internal IP. The Service is only reachable within the cluster. If you want to access the Job Manager ui or submit job to the existing session, you need to start a local proxy. You can then use
localhost:8081to submit a Flink job to the session or view the dashboard.
NodePort: Exposes the service on each Node’s IP at a static port (the
<NodeIP>:<NodePort> could be used to contact the Job Manager Service.
NodeIP could be easily replaced with Kubernetes ApiServer address.
You could find it in your kube config file.
LoadBalancer: Default value, exposes the service externally using a cloud provider’s load balancer.
Since the cloud provider and Kubernetes needs some time to prepare the load balancer, you may get a
NodePort JobManager Web Interface in the client log.
You can use
kubectl get services/<ClusterId> to get EXTERNAL-IP and then construct the load balancer JobManager Web Interface manually
ExternalName: Map a service to a DNS name, not supported in current version.
Please reference the official documentation on publishing services in Kubernetes for more information.
The Kubernetes session is started in detached mode by default, meaning the Flink client will exit after submitting all the resources to the Kubernetes cluster. Use the following command to attach to an existing session.
To stop a Flink Kubernetes session, attach the Flink client to the cluster and type
Flink uses Kubernetes OwnerReference’s to cleanup all cluster components.
All the Flink created resources, including
Pod, have been set the OwnerReference to
When the deployment is deleted, all other resources will be deleted automatically.
By default, the JobManager and TaskManager only store logs under
/opt/flink/log in each pod.
If you want to use
kubectl logs <PodName> to view the logs, you must perform the following:
rootLogger.appenderRef.console.ref = ConsoleAppender.
-Dkubernetes.container-start-command-template="%java% %classpath% %jvmmem% %jvmopts% %logging% %class% %args%".
kubectl logsto view your logs.
If the pod is running, you can use
kubectl exec -it <PodName> bash to tunnel in and view the logs or debug the process.
As described in the plugins documentation page: in order to use plugins they must be copied to the correct location in the flink installation for them to work.
The simplest way to enable plugins for use on Kubernetes is to modify the provided official Flink docker images by adding an additional layer. This does however assume you have a docker registry available where you can push images to and that is accessible by your Kubernetes cluster.
How this can be done is described on the Docker Setup page.
With such an image created you can now start your Kubernetes based Flink session cluster with the additional parameter
kubernetes.container.image which must specify the image that was created:
Extending the above example command to start the session cluster makes it this:
Namespaces in Kubernetes are a way to divide cluster resources between multiple users (via resource quota).
It is similar to the queue concept in Yarn cluster. Flink on Kubernetes can use namespaces to launch Flink clusters.
The namespace can be specified using the
-Dkubernetes.namespace=default argument when starting a Flink cluster.
ResourceQuota provides constraints that limit aggregate resource consumption per namespace. It can limit the quantity of objects that can be created in a namespace by type, as well as the total amount of compute resources that may be consumed by resources in that project.
Role-based access control (RBAC) is a method of regulating access to compute or network resources based on the roles of individual users within an enterprise. Users can configure RBAC roles and service accounts used by Flink JobManager to access the Kubernetes API server within the Kubernetes cluster.
Every namespace has a default service account, however, the
default service account may not have the permission to create or delete pods within the Kubernetes cluster.
Users may need to update the permission of
default service account or specify another service account that has the right role bound.
If you do not want to use
default service account, use the following command to create a new
flink service account and set the role binding.
Then use the config option
-Dkubernetes.jobmanager.service-account=flink to make the JobManager pod using the
flink service account to create and delete TaskManager pods.
Please reference the official Kubernetes documentation on RBAC Authorization for more information.
This section briefly explains how Flink and Kubernetes interact.
When creating a Flink Kubernetes session cluster, the Flink client will first connect to the Kubernetes ApiServer to submit the cluster description, including ConfigMap spec, Job Manager Service spec, Job Manager Deployment spec and Owner Reference. Kubernetes will then create the Flink master deployment, during which time the Kubelet will pull the image, prepare and mount the volume, and then execute the start command. After the master pod has launched, the Dispatcher and KubernetesResourceManager are available and the cluster is ready to accept one or more jobs.
When users submit jobs through the Flink client, the job graph will be generated by the client and uploaded along with users jars to the Dispatcher. A JobMaster for that Job will be then be spawned.
The JobMaster requests resources, known as slots, from the KubernetesResourceManager. If no slots are available, the resource manager will bring up TaskManager pods and registering them with the cluster.