Hello Christopher, The most common deployment of StateFun applications is via the community provided Docker images[1] (and their derivations) . This image captures the optimal deployment of Flink for StateFun. In addition, there is also an example of how to deploy these images to k8s[2]. If you are exploring SF and trying to get started, then you can simply explore the Stateful functions playground[3] and start up an entire env via docker-compose.
If your env requires deploying SF as a Flink job this is still possible, and few folks have been asking this in the past, and I'm sure you can find these threads in the archive, if not let me know and I will point you in the right direction. [1] https://hub.docker.com/r/apache/flink-statefun [2] https://github.com/apache/flink-statefun-playground/tree/release-3.1/deployments/k8s [3] https://github.com/apache/flink-statefun-playground/tree/release-3.1 All the best! Igal On Tue, Feb 1, 2022 at 11:57 AM Christopher Gustafson <chr...@kth.se> wrote: > Hi, > > > I am looking into ways to deploy StateFun jobs. I noticed that the option > of packaging a StateFun job as a fat jar to an existing flink cluster was > described in the 2.2 version of the docs > <https://nightlies.apache.org/flink/flink-statefun-docs-release-2.2/deployment-and-operations/packaging.html> > but > not in the latest versions. Is this way of deploying StateFun jobs still > supported, and in that case are there any additional steps that has to be > taken? > > Best Regards, > > Christopher Gustafson >
