You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I believe arbitrary code can do basically anything to our cluster. Isolation via namespace does work, but in that case we need to move spawner into it's own namespace (pods can still talk to each other though).
Note: This is also important for Abaco.
The text was updated successfully, but these errors were encountered:
NotChristianGarcia
changed the title
KG .35 - Need to isolate pods from network sans their open ports.
KG 0.35 - Need to isolate pods from network sans their open ports.
Jun 17, 2022
Currently I believe arbitrary code can do basically anything to our cluster. Isolation via namespace does work, but in that case we need to move spawner into it's own namespace (pods can still talk to each other though).
Note: This is also important for Abaco.
The text was updated successfully, but these errors were encountered: