I’d go for a Helm chart, where I would define FlinkDeployment, with desired pod templates and all other stuff. That other stuff can be your headless service, PVCs, CofigMaps,… In the pod template you can define also sidecars and init containers, should you need them.
Nix. From: Gyula Fóra <gyula.f...@gmail.com> Date: Tuesday, January 14, 2025 at 11:26 AM To: Yarden BenMoshe <yarde...@gmail.com> Cc: user@flink.apache.org <user@flink.apache.org> Subject: Re: [Flink kubernetes operator] custom dependent resources? Hi Yarden! You have different possibilities: - Use a podTemplate for your FlinkDeployments - Extend and build a custom operator version with your specific requirements - Use a mutating webhook to automatically create a podTemplate for every FlinkDeployment Cheers, Gyula On Sun, Dec 22, 2024 at 2:34 PM Yarden BenMoshe <yarde...@gmail.com<mailto:yarde...@gmail.com>> wrote: Hi all, I am currently using Flink via Kubernetes Operator and looking to connect my Flink pipeline to Prometheus for metrics. To do so, I thought of creating a headless service and exposing a specific port (for example 9249, Flink's default). I wish to automate the creation of the service to be created when a FlinkDeployment is created, but I believe that should be done on operator level (As I imagine the service being tightly related to the FlinkDeployment) Is this approach considered a known/common practice? If so, is there already support for such functionality, or is it something planned for a future release? Many thanks, Yarden
