The GitHub Actions job "Flink Kubernetes Operator CI" on flink-kubernetes-operator.git/FLINK-40873-overlapping-config-key-prefixes has failed. Run started by GitHub user Admaing (triggered by Admaing).
Head commit for run: 3ee891f75a27860d59e08d9f9becba985561caa4 / yongfu.gao <[email protected]> [FLINK-40873][operator] Remove overlapping config key prefixes Three operator keys are a strict prefix of another key, which makes converting a flat config map to yaml fail with "ClassCastException: String cannot be cast to Map" as soon as both sides of a pair are configured: job.autoscaler.scaling.parallelism-alignment.mode (< ...mode.<name>.*) kubernetes.operator.savepoint.history.max.age (< ...max.age.threshold) kubernetes.operator.savepoint.history.max.count (< ...max.count.threshold) Rename the top/parent property of the first pair and the newer children of the other two. The per-name alignment mode templates stay as they are: ...parallelism-alignment.mode -> ...parallelism-alignment.modes ...savepoint.history.max.age.threshold -> ...savepoint.history.threshold.max.age ...savepoint.history.max.count.threshold -> ...savepoint.history.threshold.max.count All three use withDeprecatedKeys() so existing configurations keep working. The new tests reflect over every documented ConfigOption and fail when one key is a strict prefix of another, round-trip all option keys through yaml, and cover reading the deprecated keys. Generated-by: DeepSeek Harness (deepseek-v4.1-flash) Report URL: https://github.com/apache/flink-kubernetes-operator/actions/runs/40203277345 With regards, GitHub Actions via GitBox
