[HN Gopher] Show HN: kproximate - A Kubernetes node autoscaler f...
___________________________________________________________________
Show HN: kproximate - A Kubernetes node autoscaler for Proxmox
Author : someofmyparts
Score : 51 points
Date : 2023-09-30 09:10 UTC (13 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| oneplane wrote:
| I wonder how hard it would be to port this over to a Karpenter
| variant. I suppose the Proxmox API won't do the same things as an
| AWS EC2 API so an operator-in-the-middle would still be required.
| lloydatkinson wrote:
| Infrastructure and devops becomes more abstracted with every new
| word salad.
| quadrifoliate wrote:
| I am a little tired of commenters lazily flinging this every
| time something in the infrastructure world comes up that they
| don't fully understand. Something doesn't become word salad
| just because you don't know what it means.
|
| I might have problems understanding something -- say,
| "Comparison of implementations of in-order traversal of an AVL
| tree in Scala v/s Clojure"; but that doesn't mean it doesn't
| have a clear and intelligible meaning to someone who gets it.
|
| In this case, I understand the idea here somewhat even without
| looking at the project. Kubernetes has very flexible auto-
| scaling capabilities. This seems to be be somehow allowing it
| to scale across a bunch of VMs hosted using Proxmox, which is
| an open-source VM hosting platform. There is no word salad
| about it.
| glitchcrab wrote:
| Agreed, the title was pretty self explanatory.
| jrockway wrote:
| I have heard of Proxmox but didn't really know what it did,
| so I went to Wikipedia, which tells me: "Proxmox Virtual
| Environment (Proxmox VE or PVE) is a hyper-converged
| infrastructure open-source software."
|
| This is a little buzzwordy. I am also not sure that something
| can be "a software".
| RamRodification wrote:
| English is not my first language but i think the "a" is for
| the infrastructure. It's software for a hyper-converged
| infrastructure.
|
| If you remove the "a", to me, it sounds like the software
| is hyper-converged instead. Which seems less correct.
|
| Anyway I agree. The very next couple of sentences describe
| it better in my opinion. Maybe they should put those two
| first:
|
| _" It is a hosted hypervisor that can run operating
| systems including Linux and Windows on x64 hardware. It is
| a Debian-based Linux distribution with a modified Ubuntu
| LTS kernel and allows deployment and management of virtual
| machines and containers"_
| matthews2 wrote:
| What is the benefit to running multiple Kubernetes nodes on one
| physical Proxmox machine?
| cassianoleal wrote:
| Failover, green-blue upgrades, experimentation are 3 things
| that come to mind.
| Kab1r wrote:
| Thinly provisioned compute in the presence of other VMs is one
| reason, but I think this is aimed at people with multiple
| proxmox nodes in a cluster.
| RamRodification wrote:
| > Thinly provisioned compute in the presence of other VMs is
| one reason
|
| That's the only reason I can think of.
|
| > I think this is aimed at people with multiple proxmox nodes
| in a cluster
|
| I think so too, but then we're back to the original question
| again (i.e. why not just have kubernetes nodes instead of
| having proxmox nodes with kubernetes VMs on them).
| sgarland wrote:
| You can also do things like live VM migration, where the
| K8s nodes get transferred to a different Proxmox node
| without interruption.
|
| Arguably niche, but if you have a small cluster (I have 3
| physical nodes in my Proxmox cluster at home), it's
| sometimes nice to be able to just shift everything to do
| maintenance without having to worry about losing quorum or
| disrupting workloads.
| maneesh wrote:
| If you host multiple proxmox nodes, you can host other VMs
| on each bare metal node in addition to the kid cluster,
| right?
| RamRodification wrote:
| Yes. Seems reasonable if you have much more compute than
| you can saturate with just things in your kubernetes
| cluster. Otherwise just make those hosts kubernetes nodes
| instead and call it a day.
| moondev wrote:
| Why make pets when you are already set up for cattle
| withinboredom wrote:
| Won't this just result in over-committing the physical nodes? Or
| am I missing something?
| linsomniac wrote:
| If your k8s nodes are the same height and width as your Proxmox
| servers, then yes. In my case, I have clusters of ~7 nodes, 100
| cores, 1.75TB RAM, but my VMs tend to be much, much smaller. My
| web workers are each a handful of cores, I could double them a
| couple times before saturating the physical nodes core count.
| donutshop wrote:
| Wow that is some serious horsepower.
| carlhjerpe wrote:
| Host resources might and should be overprovisioned, this
| ensures the k8s clusters you run on proxmox aren't
| overprovisioned.
___________________________________________________________________
(page generated 2023-09-30 23:01 UTC)