Dennis-Mircea opened a new pull request, #1242:
URL: https://github.com/apache/flink-kubernetes-operator/pull/1242
## What is the purpose of the change
This PR tracks canary resources only when the health probe is enabled, and
runs their health checks on a single named thread per canary manager.
## Brief change log
- `CanaryResourceManager` reads `kubernetes.operator.health.probe.enabled`
once on creation. When the probe is disabled, canary resources are still
recognized and not deployed, but they are not tracked, updated or checked.
- The health checks run on a single-thread scheduler with a named daemon
thread (`<kind>-canary-health-check-thread-1`), instead of a 3-thread pool with
generic names. The scheduler is created on the first scheduled check, and
nothing is scheduled after `close()`.
## Verifying this change
This change can be verified through the newly added tests and manually
within minikube on canary.yaml example.
## 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]
