-
Notifications
You must be signed in to change notification settings - Fork 42
refactor(controller): delegate health checks to k8s readiness probes #130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
5ae3bdb to
1f00af9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as a layman, but I'll leave the final approval to @VaishnaviHire 😄
Thanks for this @mfleader!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! I'll wait for final approval just in case, but I think this PR is a good addition to simplify the readiness check.
6f12141 to
3deaca9
Compare
…dependency injection (#133) Refactors the LlamaStackDistributionReconciler to accept an httpClient dependency. This makes the controller's status-update logic, which relies on external API calls, testable in isolation. The primary goal of this change is to enable a new integration test that validates the controller correctly populates provider and version info in the resource status. This test is added to formalize the expected behavior and prevent regressions. `checkHealth()` and its endpoint `v1/health` were not included in these changes since they will be removed in a subsequent code change, [130](#130). Approved-by: rhdedgar
8a99a83 to
61e42c5
Compare
|
Untested but code lgtm |
What about the test in |
I mean't it was untested by me (i.e. I didn't run the code locally) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, very clean
The controller now relies on the Deployment's readiness status, which is driven by a new readiness probe on the container. This removes the operator's redundant, manual health-checking logic and makes the system more robust by using a standard Kubernetes feature. Signed-off-by: Matthew F Leader <mleader@redhat.com>
Signed-off-by: Matthew F Leader <mleader@redhat.com>
5c09fcd to
9c23a53
Compare
…dependency injection (llamastack#133) Refactors the LlamaStackDistributionReconciler to accept an httpClient dependency. This makes the controller's status-update logic, which relies on external API calls, testable in isolation. The primary goal of this change is to enable a new integration test that validates the controller correctly populates provider and version info in the resource status. This test is added to formalize the expected behavior and prevent regressions. `checkHealth()` and its endpoint `v1/health` were not included in these changes since they will be removed in a subsequent code change, [130](llamastack#130). Approved-by: rhdedgar (cherry picked from commit 7cca6e4)
…lamastack#130) The controller now relies on the Deployment's readiness status, which is driven by a new readiness probe on the container. This removes the operator's redundant, manual health-checking logic and makes the system more robust by using a standard Kubernetes feature. Approved-by: rhdedgar (cherry picked from commit 2fa21ea)
…dependency injection (llamastack#133) Refactors the LlamaStackDistributionReconciler to accept an httpClient dependency. This makes the controller's status-update logic, which relies on external API calls, testable in isolation. The primary goal of this change is to enable a new integration test that validates the controller correctly populates provider and version info in the resource status. This test is added to formalize the expected behavior and prevent regressions. `checkHealth()` and its endpoint `v1/health` were not included in these changes since they will be removed in a subsequent code change, [130](llamastack#130). Approved-by: rhdedgar (cherry picked from commit 7cca6e4)
…lamastack#130) The controller now relies on the Deployment's readiness status, which is driven by a new readiness probe on the container. This removes the operator's redundant, manual health-checking logic and makes the system more robust by using a standard Kubernetes feature. Approved-by: rhdedgar (cherry picked from commit 2fa21ea)
The controller now relies on the Deployment's readiness status, which is driven by a new readiness probe on the container.
This removes the operator's redundant, manual health-checking logic and makes the system more robust by using a standard Kubernetes feature.