Hi!
This change aligns with how newer Flink 1.16+ versions handle application
job ids. There are some good reasons for doing this please see:
https://issues.apache.org/jira/browse/FLINK-19358
https://issues.apache.org/jira/browse/FLINK-29109
If you want to go back to the old behaviour you need to
Hi everyone
After updating kuberneter operator to version 1.2.0 noticed that it started
generating jobid for all deployments.
2022-10-13 06:18:30,724 o.a.f.k.o.c.FlinkDeploymentController [INFO
][infojob/infojob] Starting reconciliation
2022-10-13 06:18:30,725 o.a.f.k.o.l.AuditUtils [IN