I'd like to start a discussion on FLIP-XXX : Running Flink jobs in MiniCluster using the Kubernetes Operator https://docs.google.com/document/d/1dtGjPYcsBkx1vxHPs1QnDtPxeH_Acz_pl8gx4b1BLB4/edit?usp=sharing
The aim of the FLIP is to extend the Flink Kubernetes Operator to offer a single-pod, light-weight deployment option for low-throughput jobs. >From the motivation: A single-pod, self-contained Flink job that starts fast and needs no multi-pod coordination could be a good fit for low-throughput jobs that aren't suitable for session clusters because they need isolation. Looking forward to feedback, both on the general motivation (Have you seen a need for very small lightweight Flink jobs where fast crash-consistent resume is good enough without a full distributed Flink cluster?) and the suggested implementation approach (Do you think a new custom resource kind is the best way to represent this capability?) Kind regards Dale -- dalelane.co.uk
