The GitHub Actions job "Flink Kubernetes Operator CI" on flink-kubernetes-operator.git/FLINK-39791 has failed. Run started by GitHub user gerkElznik (triggered by gyfora).
Head commit for run: 07984a0dd68e86fd7a4b88459c2ad67909c7c02d / Gerk Elznik <[email protected]> [FLINK-39791][helm] Honor defaultConfiguration.config.yaml and always mount config.yaml The operator Helm chart rendered both a `config.yaml` and a `flink-conf.yaml` entry into the operator ConfigMap and picked which one to mount with `hasKey`. A user's `defaultConfiguration.config.yaml` was therefore silently ignored, and the operator always mounted `flink-conf.yaml` assembled from the chart defaults. Render a single `config.yaml` ConfigMap entry, resolved as `defaultConfiguration.config.yaml` when set, otherwise the legacy `flink-conf.yaml`, otherwise the chart default, and always mount it as `config.yaml` — the only file name Flink 2.x reads. Rename the chart's seed `conf/flink-conf.yaml` to `conf/config.yaml` and drop its `taskmanager.numberOfTaskSlots` and `parallelism.default` entries: both already equal Flink's compiled defaults, `parallelism.default` is managed per-deployment by the operator, and removing them lets a flat user override of those keys avoid a duplicate-key collision under Flink 2.x's strict YAML parser. This makes `config.yaml` win over `flink-conf.yaml` and reduces the ConfigMap to a single key. The values.yaml comments are restructured into two mutually exclusive format examples, the English docs are updated, and the helm-unittest suite covers the resolver precedence, the single-key shape, and the dropped-seed-key behavior. Generated-by: Claude Code (Claude Opus 4.8) Co-Authored-By: Claude <[email protected]> Report URL: https://github.com/apache/flink-kubernetes-operator/actions/runs/26790576416 With regards, GitHub Actions via GitBox
