K3k: Kubernetes in Kubernetes

(github.com)

33 points | by jzebedee 3 hours ago

8 comments

  • matt123456789 1 hour 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.
  • kitd 1 hour ago
    Missed the opportunity to call it Kink ...
  • redrove 1 hour ago
    So this is basically vCluster[0] but Rancher branded?

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

    • AlfeG 1 hour ago
      Closely related in pupopse, yes. Branded? no.
  • weitzj 39 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?
  • rjzzleep 1 hour ago
    Do Rancher side products generally make it into a stable state such that you would want to run mission-critical systems on?
    • V99 1 minute ago
      (Former employee) They tend to either get enough traction very quickly and be supported for years, or not and be abandoned in weeks/months.
    • sofixa 32 minutes ago
      RKE (their Kubernetes deployment and management platform, mostly for various flavours of self managed environments) is pretty popular with the self-managed crowd that needs something to manage their on Orem Kubernetes clusters.
  • aiman_alsari 2 hours ago
    Yo dawg...
  • bloppe 1 hour ago
    What does k3k stand for? Can we just put whatever number we want between 2 letters now?
    • BurpyDave 54 minutes ago
      I suspect it’s ‘kubernetes in kubernetes’
    • pcald 36 minutes ago
      k in k
    • stingraycharles 49 minutes ago
      I suspect it's a play on another kubernetes variant, `k3s` ?
  • madduci 1 hour ago
    Nice, now we need K3Kind