SwimSweet commented on code in PR #20671:
URL: https://github.com/apache/flink/pull/20671#discussion_r956250930
##########
docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md:
##########
@@ -97,14 +97,34 @@ COPY /path/of/my-flink-job.jar
$FLINK_HOME/usrlib/my-flink-job.jar
After creating and publishing the Docker image under `custom-image-name`, you
can start an Application cluster with the following command:
```bash
+# Local Schema
$ ./bin/flink run-application \
--target kubernetes-application \
-Dkubernetes.cluster-id=my-first-application-cluster \
-Dkubernetes.container.image=custom-image-name \
local:///opt/flink/usrlib/my-flink-job.jar
+
+# FileSystem
+$ ./bin/flink run-application \
+ --target kubernetes-application \
+ -Dkubernetes.cluster-id=my-first-application-cluster \
+ -Dkubernetes.container.image=custom-image-name \
+ s3://my-bucket/my-flink-job.jar
+
+# Http/Https Schema
+$ ./bin/flink run-application \
+ --target kubernetes-application \
+ -Dkubernetes.cluster-id=my-first-application-cluster \
+ -Dkubernetes.container.image=custom-image-name \
+ http://ip:port/my-flink-job.jar
```
+{{< hint info >}}
+Now, The jar package supports reading from the [flink filesystem]({{< ref
"docs/deployment/filesystems/overview" >}}#docker-hub-flink-images) or
Http/Https in Application Mode.
+The jar package will be downloaded from filesystem to
+[kubernetes.user.artifacts.base.dir]({{< ref "docs/deployment/config"
>}}#kubernetes-user-artifacts-base-dir)/[kubernetes.namespace]({{< ref
"docs/deployment/config" >}}#kubernetes-namespace)/[kubernetes.cluster-id]({{<
ref "docs/deployment/config" >}}#kubernetes-cluster-id) path in image.
+{{< /hint >}}
+<span class="label label-info">Note</span> `local` schema is also supported .
Review Comment:
Exactly as you said ,`/opt/job.jar` is equal `file:///opt/job.jar`.This
makes it difficult for users to distinguish whether the Jar package is on the
client machine or the container.
BTW, are there plans to support submitting user jars from the client? If
`kubernetes.rest-service.exposed.type` is set to ClusterIP, it is difficult for
clients outside k8s to connect to the jobmanager deployed in k8s.
please take a look @wangyang0918
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
