tillrohrmann commented on a change in pull request #11228: [FLINK-16293][Kubernetes] Document using plugins in Kubernetes URL: https://github.com/apache/flink/pull/11228#discussion_r395088324
########## File path: docs/ops/deployment/kubernetes.md ########## @@ -91,15 +91,28 @@ In order to terminate the Flink session cluster, use `kubectl`: ## Flink job cluster on Kubernetes -A Flink job cluster is a dedicated cluster which runs a single job. -The job is part of the image and, thus, there is no extra job submission needed. +A Flink job cluster is a dedicated cluster which runs a single job. +The job is part of the image and, thus, there is no extra job submission needed. ### Creating the job-specific image The Flink job cluster image needs to contain the user code jars of the job for which the cluster is started. Therefore, one needs to build a dedicated container image for every job. Please follow these [instructions](https://github.com/apache/flink/blob/{{ site.github_branch }}/flink-container/docker/README.md) to build the Docker image. - + +### Using plugins + +As described in the [plugins]({{ site.baseurl }}/ops/plugins.html) 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 Flink docker image 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]({{ site.baseurl }}/zh/ops/deployment/docker.html#using-plugins) page. + +With such an image created you can now start your Kubernetes based Flink cluster with image that was created. Review comment: ```suggestion With such an image created you can now start your Kubernetes based Flink cluster which can use the enabled plugins. ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
