After using namespaced kubernetes client, we will not need to always set the namespace when creating kubernetes resources(e.g. deployment, pods, configmap, watch, etc.).

Address comments: Update the unit test to verify the configmap watch is created in appropriate namespace

This closes #14570.

This closes #13755.

This closes #12277 .

[FLINK-15836][k8s] Throw fatal error in KubernetesResourceManager when the pods watcher is closed with exception

By default the watcher will always reconnect in Kubernetes client internally. However, if the watchReconnectLimit is configured by users via java properties or environment, the watcher may be stopped. Then all the changes of pods will not be processed properly. The reason why the the watcher closed exceptionally is usually because of network problems or port abuse. The correct way is to fail the jobmanager pod and retry in a new one.

This closes #11010.

[FLINK-15790][k8s] Make some interfaces in FlinkKubeClient asynchronous which potentially blocks the execution of RpcEndpoint's main thread

The interfaces in FlinkKubeClient will be called both in Client and ResourceManager. To avoid potentially blocking the execution of RpcEndpoint's main thread, these interfaces #createTaskManagerPod, #stopPod should be implemented asynchronously.

This closes #11427.

[FLINK-16598][k8s] Respect the rest port exposed by Service in Fabric8FlinkKubeClient#getRestEndpoint

This closes #11715 .

1.The REST service serves REST traffic while the internal service serves internal requests from TMs to JM.
2.The REST service is always created but the internal service is only created in non-high availability setup.
Co-authored-by: Nfelixzheng <felixzheng@tencent.com>

This closes #11456 .

[FLINK-16493][k8s] Use enum type instead of string type for KubernetesConfigOptions.REST_SERVICE_EXPOSED_TYPE

This closes #11346 .

This closes #11233 .

[FLINK-15789][kubernetes] Do not wrap the InterruptedException and throw a different one in ActionWatcher.await

This closes #10970.

This commit reduces the log noise of the Fabric8FlinkKubeClient by changing the log level
from info to debug.

This closes #10965.

The Fabric8FlinkKubeClient will be used to interact with Kubernetes API server to create/delete resources and get the status. The decorators will be used to build the complete Kubernetes resource description.

This closes #9965 .