The GitHub Actions job "CI" on flink-kubernetes-operator.git has succeeded. Run started by GitHub user mxm (triggered by mxm).
Head commit for run: b6c9cd7cdbd03b696d515060dec60b4deaaa1695 / Max Michels <[email protected]> [FLINK-31866] Start metric window with timestamp of first observation The autoscaler uses a ConfigMap to store past metric observations which is used to re-initialize the autoscaler state in case of failures or upgrades. Whenever trimming of the ConfigMap occurs, we need to make sure we also update the timestamp for the start of the metric collection, so any removed observations can be compensated with by collecting new ones. If we don't do this, the metric window will effectively shrink due to removing observations. This can lead to triggering scaling decisions when the operator gets redeployed due to the removed items. The solution we are opting here is to treat the first metric observation timestamp as the start of the metric collection. Report URL: https://github.com/apache/flink-kubernetes-operator/actions/runs/4784801298 With regards, GitHub Actions via GitBox
