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 43 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 hours ago [-]
So this is basically vCluster[0] but Rancher branded?
Do Rancher side products generally make it into a stable state such that you would want to run mission-critical systems on?
sofixa 10 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 54 minutes ago [-]
What does k3k stand for? Can we just put whatever number we want between 2 letters now?
BurpyDave 32 minutes ago [-]
I suspect it’s ‘kubernetes in kubernetes’
pcald 15 minutes ago [-]
k in k
stingraycharles 28 minutes ago [-]
I suspect it's a play on another kubernetes variant, `k3s` ?
madduci 1 hours ago [-]
Nice, now we need K3Kind
Rendered at 07:25:41 GMT+0000 (Coordinated Universal Time) with Vercel.
[0] https://github.com/loft-sh/vcluster