The GitHub Actions job "CI" on flink-kubernetes-operator.git has failed. Run started by GitHub user mbalassi (triggered by mbalassi).
Head commit for run: dc173cbccd5f9a90fe573ce01790684253dcc0a9 / Ottomata <[email protected]> [FLINK-30329] Mount flink-operator-config-volume at /opt/flink/conf without subPath When mounted volumes use subPath, the volume that uses them is not updated automatically. So, even you do update the ConfigMap in k8s, the flink-conf.yaml file will never see those updates. All of the entires in the flink-operator-config-volume configMap are mounted in each container anyway, so we might as well just mount the flink-operator-config-volume directly at /opt/flink/conf witihout specifying the subPath of each file. This allows for Dynamic Operator Configuration to work when deployed with these helm charts. https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/#dynamic-operator-configuration Report URL: https://github.com/apache/flink-kubernetes-operator/actions/runs/3677431363 With regards, GitHub Actions via GitBox
