For now we used a workaround and forked the helm charts repo and we changed in the agents deployment.yaml, instead of taking the key and secret from the clearml-conf secret we take them from another secret we created so the server does not “know” about this new key and secret and does not reset them
O k, I’d like to test it more with you; credentials exposed in chart values are system ones and it’s better to not change them; let’s forget about them for now. If you create a new accesskey/secretkey pair in ui, you should use these ones in your agents and they shuld not get overwritten in any way; can you confirm it works without touching
Hi ApprehensiveSeahorse83 , today we released
clearml-agent chart that just installs glue agent. My suggestion is to disable k8s glue and any other agent from the
clearml chart and install more than one
clearml-agent chart in different namespaces. In this way you will be able to have k8s glue for every queue (cpu and gpu).