-
Notifications
You must be signed in to change notification settings - Fork 42
Add Service Endpoint to LlamaStackDistribution .status #162
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
Add Service Endpoint to LlamaStackDistribution .status #162
Conversation
abcf933 to
9c3e2d6
Compare
|
@ChristianZaccaria please run pre-commit locally and repush. Thanks |
9c3e2d6 to
3ad1e75
Compare
Signed-off-by: ChristianZaccaria <christian.zaccaria.cz@gmail.com>
3ad1e75 to
7b6889b
Compare
|
Pre-commit seems to be stuck:
|
The workflows were awaiting approval |
Ohh I didn't know that, thanks @derekhiggins ! |
|
Confirmed working in CI
|
## Description The `.status.serviceURL` field in the `LlamaStackDistribution` resource would now have the value i.e.,: ``` http://<service-name>.<namespace>.svc.cluster.local:<port> ``` Note: the pre-commit linter seems to not like the use of `serviceUrl`. It said to use `serviceURL` instead. ## Verification Steps I tested the service by: 1. Running my own version of llama-stack-k8s-operator on OpenShift with the changes in this PR: `make deploy IMG=quay.io/rh_ee_czaccari/llama-stack-k8s-operator:servicestatus4` 2. Created a sample LlamaStackDistribution. 3. Then I ran a test pod: >kubectl run curl-test --image=quay.io/rh_ee_czaccari/curl:test5 --rm -it --restart=Never -n ollama-dist -- curl -k -v http://llamastackdistribution-sample-service.ollama-dist.svc.cluster.local:8321/v1/models Approved-by: leseb Approved-by: derekhiggins (cherry picked from commit f2e783f)
## Description The `.status.serviceURL` field in the `LlamaStackDistribution` resource would now have the value i.e.,: ``` http://<service-name>.<namespace>.svc.cluster.local:<port> ``` Note: the pre-commit linter seems to not like the use of `serviceUrl`. It said to use `serviceURL` instead. ## Verification Steps I tested the service by: 1. Running my own version of llama-stack-k8s-operator on OpenShift with the changes in this PR: `make deploy IMG=quay.io/rh_ee_czaccari/llama-stack-k8s-operator:servicestatus4` 2. Created a sample LlamaStackDistribution. 3. Then I ran a test pod: >kubectl run curl-test --image=quay.io/rh_ee_czaccari/curl:test5 --rm -it --restart=Never -n ollama-dist -- curl -k -v http://llamastackdistribution-sample-service.ollama-dist.svc.cluster.local:8321/v1/models Approved-by: leseb Approved-by: derekhiggins (cherry picked from commit f2e783f)
## Description The `.status.serviceURL` field in the `LlamaStackDistribution` resource would now have the value i.e.,: ``` http://<service-name>.<namespace>.svc.cluster.local:<port> ``` Note: the pre-commit linter seems to not like the use of `serviceUrl`. It said to use `serviceURL` instead. ## Verification Steps I tested the service by: 1. Running my own version of llama-stack-k8s-operator on OpenShift with the changes in this PR: `make deploy IMG=quay.io/rh_ee_czaccari/llama-stack-k8s-operator:servicestatus4` 2. Created a sample LlamaStackDistribution. 3. Then I ran a test pod: >kubectl run curl-test --image=quay.io/rh_ee_czaccari/curl:test5 --rm -it --restart=Never -n ollama-dist -- curl -k -v http://llamastackdistribution-sample-service.ollama-dist.svc.cluster.local:8321/v1/models Approved-by: leseb Approved-by: derekhiggins (cherry picked from commit f2e783f)
Description
The
.status.serviceURLfield in theLlamaStackDistributionresource would now have the value i.e.,:Note: the pre-commit linter seems to not like the use of
serviceUrl. It said to useserviceURLinstead.Verification Steps
I tested the service by:
make deploy IMG=quay.io/rh_ee_czaccari/llama-stack-k8s-operator:servicestatus4