The login prompt doesn’t appear (I tried removing cookies and all too)

SuccessfulKoala55 I’m getting 405 on api calls with the configuration you proposed. (btw I think USER_KEY is right, with a single underscore)

Awesome info! Thanks!
What env variable should I use?
Also maybe I can block unauthenticated access to that endpoint too, I guess clearml-agent doesn’t use it!

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

also no authentication it seems

It’s probably unrelated 😬 I’ll keep you posted.

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

Huh it works now…!

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

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

yep it was unrelated.. sorry
Thanks for your help

It's concating them together:
[WARNING] [elasticsearch] GET http://[ https://elasti ....

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. 🙂

Ok thanks for reply

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

hmm
that would be great.

yes

The dashboard doesn’t load

Ok I think I might have found the problem.

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

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

The K8sIntegration can be made into a nice operator for example and deeply integrate into ClearML itself. :grinning_face_with_star_eyes:

- 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…

I’m not using templates for k8s glue. I’m using the default operation mode which uses kubectl run. Should I use templates and specify a service in there to be able to connect to the pods?

I think the whole project can be more cloud friendly. I spent a lot of time adapting it to our k8s environment. I am willing also to contribute. I think a roadmap should be created for more k8s integration and then we can start. 🙂

So do I have to create a template yaml to be able to use this feature?

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

How is it going to access to actual pod? Is it a headless service?

Thanks a million SuccessfulKoala55 😍

oh great!
let me take a look at this. There’s a lot of custom tooling so integration is very important.

cc: FiercePenguin76 ^^^

│ urllib3.exceptions.LocationParseError: Failed to parse: ' https://elastic:xxxxxxxxxxxxxxxxx@clearml-elasticsearch-es-http ', label empty or too long │
` │ [2021-05-11 13:35:54,816] [8] [WARNING] [clearml.initialize] Could not connect to ElasticSearch Service. Retry 1 of 4. Waiting for 30sec ...