Skip to content

Conversation

@mfleader
Copy link
Collaborator

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.

@mfleader mfleader self-assigned this Jul 30, 2025
@mfleader mfleader added the exciting stuff! Just for Matt label Jul 30, 2025
@mfleader mfleader marked this pull request as ready for review July 30, 2025 17:03
Copy link
Collaborator

@nathan-weinberg nathan-weinberg left a 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!

Copy link
Collaborator

@rhdedgar rhdedgar left a 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.

@mfleader mfleader marked this pull request as draft August 5, 2025 22:06
mergify bot pushed a commit that referenced this pull request Aug 11, 2025
…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
@mfleader mfleader marked this pull request as ready for review August 12, 2025 15:29
@derekhiggins
Copy link
Collaborator

Untested but code lgtm

@mfleader
Copy link
Collaborator Author

Untested but code lgtm

What about the test in resource_helper_test.go?

@derekhiggins
Copy link
Collaborator

Untested but code lgtm

What about the test in resource_helper_test.go?

I mean't it was untested by me (i.e. I didn't run the code locally)

Copy link
Collaborator

@cdoern cdoern left a 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>
@mfleader mfleader requested review from VaishnaviHire, nathan-weinberg and rhdedgar and removed request for rhdedgar August 14, 2025 15:14
@mfleader mfleader requested review from rhdedgar and removed request for VaishnaviHire, nathan-weinberg and rhdedgar August 14, 2025 15:15
@mergify mergify bot merged commit 2fa21ea into llamastack:main Aug 14, 2025
6 checks passed
VaishnaviHire pushed a commit to VaishnaviHire/llama-stack-k8s-operator that referenced this pull request Aug 19, 2025
…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)
VaishnaviHire pushed a commit to VaishnaviHire/llama-stack-k8s-operator that referenced this pull request Aug 19, 2025
…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)
VaishnaviHire pushed a commit to VaishnaviHire/llama-stack-k8s-operator that referenced this pull request Sep 18, 2025
…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)
VaishnaviHire pushed a commit to VaishnaviHire/llama-stack-k8s-operator that referenced this pull request Sep 18, 2025
…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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

exciting stuff! Just for Matt

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants