Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
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

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?

  
  
Posted one year ago
Votes Newest

Answers 4


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

  
  
Posted one year ago

I didn’t get the point, if you need to change it, you can just override image name and tag by Helm

  
  
Posted one year ago

JuicyFox94 maybe you can help here?

  
  
Posted one year ago
493 Views
4 Answers
one year ago
one year ago
Tags