Reputation
Badges 1
53 × Eureka!and are you sure you mongodb respawned on same node?
Did you applied any configuration to apiserver?
you will probably need a metrics-server on your k8s
about autoscaling it’s a complex topic regarding platform management in this case. ClearML glue simply spawn pods with resources defined in template.
Just to be sure we are in sync 😁
probably
is not accessible from your pod
Hi, helm show readme
should output informations on any single parameter fo the chart. helm show values
will show the entire values file containing also the structure.
did you tried to create a debug pod with a mount using ceph storageclass? you can start from here https://downey.io/notes/dev/ubuntu-sleep-pod-yaml/ then add the pvc and the mount. then you should exec into the pod and try to write a dummy file on the mount; I suspect the problem is there
if they are in kubernetes you can simply use k8s glue
it’s pretty strange to me about the fact you can’t write on it
ok got it, are you able to access the system bypassing nginx with http://<Server Address>:8080
?
but TaskTypes is under Task
pretty weird; I have some issues with ceph in the past but never something like that
pretty strange, I also noticed in example from line 2from clearml import TaskTypes
adding @<1523701087100473344:profile|SuccessfulKoala55> to the conversation because I’m not totally sure the problem relies on ingress, it looks to be a bad token but it shouldn’t since init was good
it should be ok, for dependency charts (mongodb/elastic/redis) you need to check values by the owner (link is in valus.yaml sections)
not sure if provisioner did something unexpected
really weird, can you try to totally remove any cookie domain related?
still need time because I have two very busy days
url returning 401 is same as one exposed by ingress (if you are using them ofc)?
btw I think it's related clearml-task
usage; did you try to create a pipeline with decorators creating it with clearml-task
before?
Hi Martin 😄 ok got it but now the question: how I can pass this to the train-agent deployed with Helm chart?
it’s usually needed for autoscaler to decide when and how to scale up and down
so you are using docker-compose?