K3k: Kubernetes in Kubernetes

(github.com)

27 points | by jzebedee 3 hours ago

8 comments

  • weitzj 2 minutes ago
    I don’t understand how they are separating security in the virtual mode as they only mention pods. It seems every workload still shares the underlying node, even when in virtual mode. Take for example the OCI cache on the nodes. What about cache poisoning?
  • matt123456789 27 minutes ago
    This is, if I had to guess, a monument to a small team's stubborn insistence that such a thing could be done at all. If I can hope for a reward for them, may it be that they are allowed to hand off maintaining it to another team.
  • redrove 1 hour ago
    So this is basically vCluster[0] but Rancher branded?

    [0] https://github.com/loft-sh/vcluster

    • AlfeG 57 minutes ago
      Closely related in pupopse, yes. Branded? no.
  • kitd 1 hour ago
    Missed the opportunity to call it Kink ...
  • rjzzleep 48 minutes ago
    Do Rancher side products generally make it into a stable state such that you would want to run mission-critical systems on?
  • aiman_alsari 1 hour ago
    Yo dawg...
  • bloppe 38 minutes ago
    What does k3k stand for? Can we just put whatever number we want between 2 letters now?
    • BurpyDave 17 minutes ago
      I suspect it’s ‘kubernetes in kubernetes’
    • stingraycharles 13 minutes ago
      I suspect it's a play on another kubernetes variant, `k3s` ?
  • madduci 51 minutes ago
    Nice, now we need K3Kind