Hi community,
I would like to ask how one can clear Flink's k8s operator state.
I have a sandbox k8s cluster with Flink k8s operator where I've deployed
Flink session cluster with few Session jobs. After some play around, and
braking few things here and there I see this log:
023-09-04 21:10:30,923 o.a.f.k.o.r.d.AbstractFlinkResourceReconciler [INFO
][default/basic-session-job-only-example-5] Not ready for reconciliation
yet... │
│ 2023-09-04 21:10:45,928 o.a.f.k.o.c.FlinkSessionJobController [INFO
][default/basic-session-job-only-example-5] Starting reconciliation
│
│ 2023-09-04 21:10:45,929 o.a.f.k.o.r.s.SessionJobReconciler [WARN
][default/basic-session-job-only-example-5] Session cluster deployment is
not found │
│ 2023-09-04 21:10:45,930 o.a.f.k.o.r.s.SessionJobReconciler [WARN
][default/basic-session-job-only-example-5] Session cluster deployment is
not found │
│ 2023-09-04 21:10:45,930 o.a.f.k.o.r.d.AbstractFlinkResourceReconciler
[INFO ][default/basic-session-job-only-example-5] Not ready for
reconciliation yet...
The "basic-session-job-only-example-5" was one of by session jobs deployed
on the cluster. I reinstall operator by calling helm uninstall and kubectl
delete -f
https://github.com/jetstack/cert-manager/releases/download/v1.8.2/cert-manager.yaml
so basically trying to revert what is described at [1]. After that I've
install operator again as described in [1] but I still have those logs.
Couple of extra things:
k get pods
NAME READY STATUS RESTARTS
AGE
flink-kubernetes-operator-5dc99cb4d8-6lv88 2/2 Running 0
39m
k get services
NAME TYPE CLUSTER-IP EXTERNAL-IP
PORT(S) AGE
flink-operator-webhook-service ClusterIP 10.97.169.70 <none>
443/TCP 39m
kubernetes ClusterIP 10.96.0.1 <none>
443/TCP 13d
k get deployments
NAME READY UP-TO-DATE AVAILABLE AGE
flink-kubernetes-operator 1/1 1 1 39m
If anyone would wonder, the exact instruction on how I "broke" this is
described here [2]. However at this point what I would like to know is how
to have a clear k8s operator state.
[1]
https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.6/docs/try-flink-kubernetes-operator/quick-start/
[2]
https://github.com/kristoffSC/FlinkK8sControllerPoC/blob/ExceptionInOperator-clusterRestart/doc/K8sException_1.MD