Dennis-Mircea opened a new pull request, #1225:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1225
## What is the purpose of the change
This PR fixes the unhealthy informers check, which was previously performed
only for unhealthy event sources, excluding the healthy ones.
## Brief change log
- `InformerHealthSummary. fromRuntimeInfo` now iterates through the
controller's `informerEventSourceHealthIndicators()` event sources, instead of
event sources obtained from
`unhealthyInformerWrappingEventSourceHealthIndicator()` controllers.
## Verifying this change
The change can be verified by the new test added.
The change was also verified manually on minikube and the operator no longer
reports "All informers are unhealthy" for the case described in the JIRA.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changes to the `CustomResourceDescriptors`:
no
- Core observer or reconciler logic that is regularly executed: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change the checkbox below to `[X]` followed by the name of the tool, and
uncomment the
"Generated-by" line. See the ASF Generative Tooling Guidance for details:
https://www.apache.org/legal/generative-tooling.html
You are responsible for the quality and correctness of every change in this
PR
regardless of the tooling used. Low-effort AI-generated PRs will be closed.
See
AGENTS.md for the full guidance.
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name and Version]
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
