Reputation
Badges 1
2 × Eureka!@<1523701070390366208:profile|CostlyOstrich36> , my container section is completely empty and unspecified.
The only place I can see "ubuntu:18.04" being specified is in the clearml-agent helm chart defaults ( None ), but the whole point of me runnining --set agentk8sglue.defaultContainerImage="python:3.11-bullseye"
is that it's supposed to override that d...
@<1523701087100473344:profile|SuccessfulKoala55> , where/how is this specified, because we are not setting this image anywhere. We are trying to override with a different image "python:3.11-bullseye". If my current way of overriding is incorrect, what is the correct way of doing this?
Hi @<1749602841338580992:profile|ImpressionableSparrow64> , I have a clearml-agent in my k8s cluster and I also have my clearml-api-keys stored as a secret inside my cluster and I would like to refer to it using: 'existingClearmlConfigSecret'. If my secret was created like so:
kubectl create secret generic clearml-api-secret \
--from-literal=agentk8sglueKey="CLEARML_API_ACCESS_KEY" \
--from-literal=agentk8sglueSecret="CLEARML_API_SECRET_KEY"
do I then just set `existingClearm...
actually never mind, I was able to figure it out.