Gyula Fora

Hi! Could you please explain why you think this is a good addition? In general we should try to keep the README small and link the docs instead.

It would be great to integrate this into the regular docs but the problem I see is that this is not actually “documentation “ . it only lists the possible...

I think this makes sense but what about the following way: 1. Add the current parameter descriptions to the values yaml from the docs. 2. Remove current docs table 3....

We had a similar attempt in the past that was abandoned: https://github.com/apache/flink-kubernetes-operator/pull/170 Could you please check and explain what is different now?

Hi @tedhtchang ! I have a few general concerns regarding this PR and whether this should be part of the official documentation: 1. The Flink Operator package on operatorhub is...

Should we close this PR until there was a discussion and consensus on the dev list?

Yes @tedhtchang please do that. If you could write a small proposal of the benefits and what it would mean with regards to maintenance, release process etc compared to what...

I think it makes sense to throw a fatal error in those cases, I agree. Ideally we should have a good way to expose framework level errors to the implementing...

I think when the informer for a specific namespace cannot be created, we need to remove that namespace from the config and clear the caches. The general problem with the...

No I am not really proposing anything about newly added namespaces. What I am proposing if at any time any watched namespaces becomes unaccessible we should be able to remove...