Hi Frank!
Thank you for the interest.
As the others said, the flink-kubernetes-operator will give you quicker
job/cluster startup time together with full support for the application
mode.
Production readiness is always relative. If I had to build a new production
use-case I would not hesitate to
@Gyula Fóra is trying to prepare the preview
release(0.1) for flink-kubernetes-operator. It now is fully functional for
application mode.
You could have a try and share more feedback with the community.
The release-1.0 aims for production ready. And we still miss some important
pieces(e.g. FlinkS
Hello David,
Thanks for the information! So the two main takeaways from your email are to
- Move to something supporting application mode. Is
https://github.com/apache/flink-kubernetes-operator already ready enough
for production deployments ?
- wait for flink 1.15
thanks!
Frank
On
Hi Frank,
I'm not really familiar with the internal workings of the Spotify's
operator, but here are few general notes:
- You only need the JM process for the REST API to become available (TMs
can join in asynchronously). I'd personally aim for < 1m for this step, if
it takes longer it could sign
