chatbot-rag-app: adds Kubernetes manifest and instructions#396
chatbot-rag-app: adds Kubernetes manifest and instructions#396codefromthecrypt merged 7 commits intomainfrom
Conversation
codefromthecrypt
requested review from
EvelienSchellekens,
bshetti,
estolfo,
joemcelroy,
stanek-michal,
trentm and
xrmx
|
note: each thing we do runs back into this. it would be great to have a way to quickly initialize elser not just installing it, but first time use without timeouts for several minutes #307 |
|
I have work almost done to make this "normal k8s" local, but wanted to solve the timeout first. so I'll push commit after #397 is merged |
|
will bump this tomorrow or when an approver looks at #397 |
codefromthecrypt
force-pushed
the
k8s-chatbot-rag-app
branch
from
9f0bb96 to
3660c11
Compare
|
rebased and changed to non-host network k8s. will leave this in draft until #397 is merged as using not-yet-deployed images in k8s is a pain. |
|
waiting to get the docker image smaller before "ready for review", as I noticed my network lagging #407 |
codefromthecrypt
force-pushed
the
k8s-chatbot-rag-app
branch
from
3660c11 to
5145b72
Compare
|
ok things work in general, but I'm not seeing traces in kibana. I have to put this down for a bit as I have other more urgent things to address. |
k8s/README.md
Outdated
|
|
||
| Note: If you haven't checked out this repository, all you need is one file: | ||
| ```bash | ||
| wget https://raw.githubusercontent.com/elastic/elasticsearch-labs/refs/heads/main/docker/docker-compose-elastic.yml |
There was a problem hiding this comment.
Think this is wrong file
|
Due to elasticon singapore and Sydney... while excited about this i am not finishing it this weekend. Maybe Tuesday |
Signed-off-by: Adrian Cole <[email protected]>
Signed-off-by: Adrian Cole <[email protected]>
codefromthecrypt
force-pushed
the
k8s-chatbot-rag-app
branch
from
8b19999 to
c56190f
Compare
Signed-off-by: Adrian Cole <[email protected]>
|
hmm getting gcp auth errors will look into it |
Signed-off-by: Adrian Cole <[email protected]>
|
GCP vertex now works. I will look into why traces aren't. @bshetti I can't hold this PR captive for all issues, as once this is in it is easy to complete other topics. So, let's leave elastic cloud commentary for the next PR #379 This one is solving as-is for k8s, and it has been dozens of hours just on that! |
Signed-off-by: Adrian Cole <[email protected]>
Signed-off-by: Adrian Cole <[email protected]>
|
Also verified the kubernetes without chatbot-rag-app, rather with pydantic-ai and works fine 
|
|
create-index (doesn't use an LLM, just elastic) 
chat (proves vertex works) 
|
|
in this case I followed the directions in the README with a completely blown away k8s ( |
Signed-off-by: Adrian Cole <[email protected]>
|
OK, what I did was ran with the normal instructions, but azure openai (so no secret). It worked fine. Then, I deleted the configmap and edited in the vertex settings to recreate it, then added the secret as README said, then applied and worked fine. 
Thanks for the eagle eyes @anuraaga I think finally this one is ready to merge! |
| - name: gcloud-credentials | ||
| secret: | ||
| secretName: gcloud-credentials | ||
| optional: true # only read when `LLM_TYPE=vertex` |
There was a problem hiding this comment.
this part allows vertex config to work, but others to not block on it. the optional applies indirectly to a mount that uses it, so no worries.
4 participants
Decided to action this so that we have a coherent experience between docker compose and k8s. This is as close as I could get it. If folks have feedback or a different direction, do tell!
Fixes #366