Hi

We are looking at running Flink on Kubernetes in Job cluster mode. As part
of our plans we do not want to allow modifications to the job cluster once
a job is running. For this we are looking at a "read-only" Flink UI, that
does not allow users to cancel a job or submit a job.

My question is,
1. Is there such an option when we bring up a Flink cluster currently
2. If no, is this something we can contribute?

I can imagine another solution where the "cancel" and "submit job" options
mutates the job clusters.

Wanted to check what are the general guidelines on this.

Any pointers would be appreciated

Uday

Reply via email to