This command will help you download the user JARs without depending on the
Filesystem CLI and init-container, as shown in the attached image. It
handles the host path in Kubernetes, ensuring that only one process
downloads the JARs while the other waits for it. This can also be used in a
session cl
Hi David,
Sorry I missed your reply.
>>>Since you're mentioning docker, I assume you're deploying your
application to k8s. Is that correct?
yes, I am using k8s.
>>>For handcrafted Kubernetes deployments, you can simply download the jar into
the user lib folder in an init container [1]. You can
Hi Surendra,
Since you're mentioning docker, I assume you're deploying your application
to k8s. Is that correct?
For handcrafted Kubernetes deployments, you can simply download the jar
into the user lib folder in an init container [1]. You can usually reuse
existing docker images to download the
Hi Team,
According to the Flink documentation, in the APP mode, the application jar
should be bundled with the Flink image. However, building an image for each
new application can be difficult. Can we introduce new commands that will
help to download the required jar locally before starting Flin
