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
Hey, So I’Ve Deployed Clearml On K8S Through The Helm Charts Repo But The Left Side Menu Is Not Visible..

Hey, so I’ve deployed clearml on k8s through the helm charts repo but the left side menu is not visible..

  
  
Posted 3 years ago
Votes Newest

Answers 32


ScrawnyLion96 , Hey 🙂
Can you provide a screenshot?

  
  
Posted 3 years ago

sure

  
  
Posted 3 years ago

image

  
  
Posted 3 years ago

cloned the repo “clearml-helm-charts”

  
  
Posted 3 years ago

Interesting, try hitting F12 and refreshing the page. See if there are any errors in the console.

  
  
Posted 3 years ago

users.get_preferences
users.get_current_user
Post reqs fail…

  
  
Posted 3 years ago

Reqs to the api

  
  
Posted 3 years ago

When I deployed it without cloning the repo the menu was visible, but I need the charts locally

  
  
Posted 3 years ago

This looks like the webapp can't communicate with the apiserver

  
  
Posted 3 years ago

ScrawnyLion96 did you install the chart as explained in the repository's readme?

  
  
Posted 3 years ago

Can you provide some logs?

  
  
Posted 3 years ago

Yes

  
  
Posted 3 years ago

image

  
  
Posted 3 years ago

simple helm install, didn’t change anything in values

  
  
Posted 3 years ago

Can you show the logs for the apiserver pod?

  
  
Posted 3 years ago

image

  
  
Posted 3 years ago

Returned 400 for users.get_current_user in 3ms, msg=Invalid user (failed loading user)

  
  
Posted 3 years ago

JuicyFox94 any idea?

  
  
Posted 3 years ago

Ok found the problem

  
  
Posted 3 years ago

what was it?

  
  
Posted 3 years ago

I had an old cookie from an old deployment that’s why it didn’t recognize my user…

  
  
Posted 3 years ago

ah...

  
  
Posted 3 years ago

The cookie has a ttl of 3000+ years…

  
  
Posted 3 years ago

maybe change the session cookie to 24 hours?

  
  
Posted 3 years ago

You can. The server setting for that is auth.cookies.max_age: <int value> in the apiserver.conf file

  
  
Posted 3 years ago

Default value is indeed 99999999999 🙂

  
  
Posted 3 years ago

I’m guessing if I can set it trough Helm chart by default, will investigate by the end of the week, ty ScrawnyLion96 to point me on this interesting behavior!

  
  
Posted 3 years ago

JuicyFox94 for reference, as with all configuration values set through the configuration files, this can also be set by env vars, like so: CLEARML__APISERVER__AUTH__COOKIES__MAX_AGE=86400 representing a day in seconds

  
  
Posted 3 years ago

Yes that would be awesome

  
  
Posted 3 years ago

Thanks guys

  
  
Posted 3 years ago
20K Views
32 Answers
3 years ago
8 months ago
Tags