Yesterday I executed an experiment in our hosted clearML cluster. After the experiment was finished, we got an AWS guard duty notification about suspicious outbound traffic from the EC2 that executed the job. It looks like the tag being used is hardcoded to 1.24-18. Was this issue identified and fixed in later versions?
It looks like the tag being used is hardcoded to 1.24-18. Was this issue identified and fixed in later versions?
BoredHedgehog47 what do you mean by "hardcoded 1.24-18" ? tag to what I think I lost context here
I didn’t get the point, if you need to change it, you can just override image name and tag by Helm
