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
I Have A Kubernetes Setup Of Clearml 1.7.2 Done With The Official Helm Charts. When I Upgrade To The Latest Version Of Clearml With The Newest Helm Charts, Will The Existing Data Be Migrated (Mongo, Elastic, Redis) ?

I have a Kubernetes setup of ClearML 1.7.2 done with the official Helm charts. When i upgrade to the latest version of ClearML with the newest Helm charts, will the existing data be migrated (Mongo, elastic, redis) ?

  
  
Posted one year ago
Votes Newest

Answers 17


internal migrations are directly done by apiserver on startup

  
  
Posted one year ago

Can you pls share helm list output?

  
  
Posted one year ago

i only use ClearML, not the agent. I use this: None

  
  
Posted one year ago

Ok, what I need is the exact version of the chart (not app) for clearml and clearml-agent

  
  
Posted one year ago

\o/

  
  
Posted one year ago

these are steps for major upgrade to latest chart version

  
  
Posted one year ago

Migration worked ! Thx !

  
  
Posted one year ago

btw as general rule, it’s always safer to take a data backup before a chart upgrade regardless of version level

  
  
Posted one year ago

ok so you are on chart major verison 4 while we are now on 6. Let me check one minute pls

  
  
Posted one year ago

i use ArgoCD for deployment of the helm charts, so i have no Helm output

  
  
Posted one year ago

ok thx a lot, i will try that and do backup of all before.

  
  
Posted one year ago

Hi @<1547390444877385728:profile|ThickSnake12> , there is no migration required from the version you specify to the latest version. However, since the official helm chart has had major changes and revisions, you would need to make sure you configure it correctly and that the PVs used to store the data as assigned correctly. Perhaps @<1523701827080556544:profile|JuicyFox94> can offer some advice?

  
  
Posted one year ago

wohoo

  
  
Posted one year ago

Just to be sure

  
  
Posted one year ago

but you are starting from major for that is really old and where naming was potentially unconsistent some time so, my suggestion is to backup EVERY pv before proceeding

  
  
Posted one year ago

Thx for the response. I need to update because 1.9 has new features i want to use. I looked into the helm charts, there are no hooks to run a (data) migration, so my question will be more if 1.9 works with the same PVC data from 1.7.2

  
  
Posted one year ago
1K Views
17 Answers
one year ago
one year ago
Tags