redkubes / otomi-core

Application Platform for Kubernetes

Home Page:https://otomi.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

TTY shell breaks when another admin opens shell session

Ani1357 opened this issue · comments

Describe the bug: (a clear and concise description of what the bug is)
It seems that when more than one admin users try to access the TTY Console, it will break for the one that created it first. This is probably related to the way the kubeconfig is generated.

Expected behaviour would be to have two separate instances that do not interfere with each other.
Admin account shell should not cause conflicts with other admin shells.

To Reproduce
Steps to reproduce the behavior:

  1. Log in to otomi with an admin account
  2. Click the shell button and wait for it to load
  3. Check that you can see all namespaces k get ns
  4. On another browser(or incognito mode) log in as another admin (create account in keycloak)
  5. Click the shell button and wait for it to load
  6. Now if you run again k get ns on the old shelll it will show an authorisation error.

Expected behavior: (a clear and concise description of what you expected to happen)
Expected behaviour would be to have two separate instances that do not interfere with each other.
Admin account shell should not cause conflicts with other admin shells.

Screenshots: (if applicable, add screenshots to help explain your problem)

Cluster(s):

  • Cloud: [e.g. aws]
  • Cluster: [e.g. demo]

Versions: (seen in console's /settings)

  • Core Version [e.g. 0.12.34]
  • Console Version: [e.g. aws]
  • API version: [e.g. 0.4.56]

Desktop: (if relevant)

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone: (if relevant)

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context: (add any other context about the problem here)

great ticket description btw!