Reputation
Badges 1
53 × Eureka!it’s usually needed for autoscaler to decide when and how to scale up and down
on OSS it’s usually the only way to as many agent deployments for any queue you define
output_dest works:)
About last point: I would like to retrieve the pipeline 'output_dest' and use it as a parameter in adding steps, is that possible?
this will make autoscaler life easier knowiing exactly how much resources you need
today I'm in the middle of sprint plannings for my team so I will not be probably fast to help if needed, but feel free to ping me just in case (I will try to do my best)
I mean this blob is then saved on the fs
then I enqueue it and it's created but obv empty
this configuration object is stored as a file in /root/.trains
?
perfect, now the whole process is clear to me
and I will give you feedback here
just a couple of info
this one should not be needed for asyncdelete, what is the error you are getting?
ok the issue must be there, After first creation nothing is there
probably
is not accessible from your pod
accessing apiserver from a pod doesn’t require kubeconfig
hi, pls check first message on this pr conversation; there is a checklist to be completed otherwise CI will not complete
I need to investigate, ScrawnyLion96 can you pls open an issue on https://github.com/allegroai/clearml-helm-charts ?
btw, judging from screenshots services are ok but pod are not up, especially elastic, redis and mongodb are Pending
so it means k8s didn’t scheduled them for some reason you can find describing these pods
Did you use any override values.yaml file for this installation ?
btw as general rule, it’s always safer to take a data backup before a chart upgrade regardless of version level
ok so you are on chart major verison 4 while we are now on 6. Let me check one minute pls
Ok, what I need is the exact version of the chart (not app) for clearml and clearml-agent
yes, exactly, agent creates and manages task pod lifecycle