Nvidia Kubernetes Engine (NVKE)

Posted by gkapur 14 hours ago

Comments

Comment by QuentinM 10 hours ago

This is for tenant-isolated k8s clusters using NVIDIA's DSX reference stack, relying on NICo / BlueField to set up isolated networking, and wipes/re-attests each host between tenants. Mostly useful if you're chasing NVIDIA Cloud Partner status or need NVIDIA support across the whole stack.

Comment by eel 3 hours ago

> Mostly useful if you're chasing NVIDIA Cloud Partner status or need NVIDIA support across the whole stack.

What if I don't care about the cloud partner status or support, but I still have a lot of Nvidia hardware I need to hand out to run isolated workloads? Seems like deploying straight k8s is the way to go?

Comment by itintheory 2 hours ago

I'm not super familiar with this tool, but I am a k8s administrator. I think it depends on how isolated you need those workloads to be. This seems like a good fit if you want cluster level isolation. There are other projects that implement the Cluster API (CAPI) though, which provide similar functionality, eg declaratively managing tenant clusters.

Comment by websap 7 hours ago

Its great to see them open source this stack!

Lots of negativity from HN posters who usually manage 3 Kubernetes clusters in a single region via a managed service on AWS or GCP.

Comment by 7 hours ago

Comment by debarshri 7 hours ago

I got lot of hate too when I tried building a api server compatible engine in rust [1]

[1] https://github.com/debarshibasak/superkube

Comment by random3 12 hours ago

I just got flashbacks of stuff I forgot long ago like OpenStack and EMC Rex-ray and so many things like that https://www.openstack.org https://github.com/rexray/rexray

Comment by esseph 12 hours ago

I am seeing a lot of openstack around since Broadcom enraged the vast majority of their vmware customers

Comment by Datagenerator 10 hours ago

Just deployed OpenStack by using the Kolla Ansible installer. Works great coupled to Ceph for storage. Thanks to Broadcom we are moving in the right direction. Proxmox as fallback plan but it looks like OpenStack is solid.

Comment by 11 hours ago

Comment by Yasuraka 10 hours ago

This seems to mix several (should-be) distinct concerns like CAPI, Kamaji and gpu-operator.

The only things I'd take from this is the kind-based bootstrapper for the management cluster and SPIFFE/TPM integration.

Comment by asaiacai 9 hours ago

yeah i wish more visibility would go towards CAPI, Kamaji.

tbh i'm not sure from reading this why you wouldn't just roll rke2/k3s if the concern is an environment outside of the well worn hyperscaler managed k8s

Comment by jimbokun 12 hours ago

Can’t regular Kubernetes also deploy to GPUs?

Comment by yjftsjthsd-h 11 hours ago

Yes. https://kubernetes.io/docs/tasks/manage-gpus/scheduling-gpus...

Comment by jeremy_carroll 13 hours ago

This is what happens when AI generates your PR – FAQ. Describe what the product does versus just a data dump.

Comment by chandlerh 13 hours ago

I’m usually in agreement with this sentiment, but they do say what it is in the first paragraph.

“NVIDIA Kubernetes® Engine (NVKE) provides the management plane that platform teams install to create and operate Kubernetes clusters for their customers.”

Comment by hedora 12 hours ago

Ok, so say I have a platform team to install k8s or k3s. Why do I need NVKE? Also, how do I resell my kubernetes to customers? Like is there stripe integration?

I am more confused by its description than by just reading the product name and guessing.

Comment by Foobar8568 10 hours ago

Well one needs to read a bit more to understand what that meant...

NVKE is not a Kubernetes distribution and not a Cluster API flavour. It is a self-hosting factory for Kubernetes clusters: a throwaway seed cluster stands up a management cluster, and the management plane on it then provisions and lifecycle-manages many isolated workload clusters on demand.

Comment by adastra22 12 hours ago

That doesn’t say anything. It doesn’t answer a single question I would have.

Comment by Renina 7 hours ago

[flagged]

Comment by topspin 13 hours ago

A mention of something Kubernetes related reached the front page! A few years ago, BAI, there was one or more k8s headlines gracing HN's front page at all times.

Kinda glad that ended. k8s is fine and all, but it was a bit much for a while there.

Comment by luipugs 13 hours ago

Did you just make an acronym that means "before AI"?

Comment by topspin 12 hours ago

I did, but I'm not the first. I thought maybe I was, so I checked: apparently it's been bouncing around informally among academics for a while now. I hadn't previously seen it though, so I can at least say I came up with it independently.

I come up with things from time to time. At least one US registered trademark is mine.

Comment by wannabe44 12 hours ago

Future history books will be like: ancient legacy technology conglomerate Google was founded around 24BAI

Comment by qlte 11 hours ago

I'd guess us throwing around the word "AI" constantly and endlessly debating p(doom) based on current tech will be considered pretty amusing in the future.

Like reading essays from the late 19th century that can't stop pontificating about living in a boundless technological singularity thanks to railroads and the telegraph. Current hackocalypse discourse already has shades of "the bomber always gets through" from the 20s.

"Sure, people in every era since the Renaissance have foolishly believed they were the ones living on the cusp of uniquely transformative and potentially cataclysmic technological change but ... This Time It's Different"