ah let me try sth

It's still not connecting XD
but parsing is successful 😄

no. tried many variations. I'm not sure if it's reading the variable or not. because wait times don't change either

I changed them and tried some combinations to no avail...
I assume it should change the retry pattern too. but it doesn't change.. I feel I'm missing something obvious here

it is indeed parsing because invalid hocon leads to error. but nothing changes about retry times etc

I'll try that. How can I make it to use authentication too?

yes. Tuple is not valid. like json. only scalar, string, dict or array

there's no log of connecting to elasticsearch now 😕
does it mean it is okay?

the api server doesn't come up though. readiness probe fails.

That wouldn't have crossed my mind especially when it's not in the docs.

curl works with the same url and creds from the container...

I'm using a simple pyhocon code to test it and it won't decode. So it won't reach the code to ovverride settings at all.

standard URI
according to:
https://elasticsearch-py.readthedocs.io/en/v7.12.1/#tls-ssl-and-authentication

yes

Okayyy. I'll try this. Thanks for your help Jake!

no...

Hey Martin.
I’m deploying to k8s and want to know if PVC is necessary for Redis.

also no authentication it seems

I want to find a good deployment framework (if exists) and integrate it into our ClearML workflow).
like get latest release with prod tag from clearml api and apply that to k8s.
something along those lines

That's right

wow man you're the best!
SuccessfulKoala55

Yes.
ClearML has all these awesome dashboards. I was thinking maybe there will be some deploy to prod/staging/shadow button so you can do everything from there. (Like Gitlab CI/CD if you have seen that)
That would be ideal.

nope no luck

https://github.com/allegroai/clearml-server/blob/babfcbb70701fc725448556d1e691cdfd1292949/apiserver/es_factory.py

https://allegro.ai/clearml/docs/docs/deploying_clearml/clearml_server_config.html

I can have much more flexibility and security using Kubernetes native approaches. I can host multiple sessions behind a single LB with different host headers etc. A lot of possibilities. 🙂

hmm
that would be great.

I actually got the idea to disable istio for the container. I think that'll work considering api-server doesn't need to be accessed directly from outside.

I'll test that and then your approach. If nothing works then I'll post again 😄

Thanks for your help Jake

- name: CLEARML__APISERVER__PRE_POPULATE__ENABLED value: "false" - name: CLEARML__APISERVER__PRE_POPULATE__ZIP_FILES value: /opt/clearml/db-pre-populate - name: CLEARML_SERVER_DEPLOYMENT_TYPE value: helm-cloud

The rest are clearly credentials…

of course because the tuple is valid in Python.
but there's no way I can supply a tuple in the HOCON format (of json for that matter(

I’m using cloud-ready helm chart (with some modifications)
So for api-server deployment: