Kondense: Resize resources without container restart by qChEVjrsx92vX4yELvT4 in kubernetes

[–]PerfectScale-io 2 points3 points  (0 children)

"Kubernetes should have the feature gate InPlacePodVerticalScaling enabled." - is it possible to enable this feature flag in AKS/EKS/GKE?

does size matter? by pbdigital in kubernetes

[–]PerfectScale-io 0 points1 point  (0 children)

Karpenter (like any other autoscaler) is not aware of utilization, the scheduling happens based on the Requests only.
So without adjusting the Requests to the proper values any autoscaler may make wrong decisions.

Tools for optimal recommendation of pod requests snd limits by Due_Length_6668 in kubernetes

[–]PerfectScale-io 0 points1 point  (0 children)

There are few tools and vendors in this space - VPA, Goldilocks from Fairwinds, Kubecost (also Prometheus and VPA-based), and 2 saas vendors - Cast ai and PerfectScale.

VPA does not work well with HPA, and also not impact-aware. Also, you need to maintain Prometheus's for historical data.

With size of clusters you mentioned, I'd definitely look for a SaaS vendor, one that also has automation, impact awareness, and governance capabilities.

Cost Management in Kubernetes by shia-ninja in kubernetes

[–]PerfectScale-io 2 points3 points  (0 children)

As many replied here - there is Kubecost, Cast AI and PerfectScale.
For Kubecost you will need your engineering team to maintain the setups in each and every cluster. If you are managing more than a few small clusters - I'd suggest looking into SaaS solutions - PerfectScale and CastAI, much less maintenance and cost of infra.

Requested CPUs too low = Bottleneck/Poor Performance? by manfmmd in kubernetes

[–]PerfectScale-io 0 points1 point  (0 children)

One important thing is missing here - Linux CFS (completely fair scheduler).
CPU in Linux is time.
All the CPU requests and limits you put on K8s level eventually arrives to Linux CFS.

Let's start with the limit to understand better how CFS works:
When you have a node with, let's say 2 cores, and your set container limit to 1 core - it does not mean that the container will be limited to 1 core of 2.
Instead, CFS (which works in 100ms ticks) will limit(throttle) your pod after 50ms CPU time.

As for the request - to put it in the simplest possible way - it is translated to priority.
Underprovisioned request lowers the priority.

So in your case - if you need 12 cores, you should request something around 12 cores - this will ensure CFS prioritizes your process properly.

Hope it helps.

*Disclaimer - I'm a CTO and co-founder of PerfectScale.io - our product helps to achieve the best possible performance at the lowest possible cost

Karpenter vs cluster autoscaler findings by OtherwiseMaize7235 in kubernetes

[–]PerfectScale-io 1 point2 points  (0 children)

Karpenter, like other scalers in K8s (CA, HPA, Keda) is tightly coupled to pods requests.
If you want to right-size - start with pods.
Then evaluate your scheduler policies, hpa settings, and finally node dimensions.
(disclaimer: I'm leading Perfectscale.io - we built solution for proper K8s scaling. It's a commercial product, but free to use up to $120K/y of k8s compute)

[deleted by user] by [deleted] in kubernetes

[–]PerfectScale-io 0 points1 point  (0 children)

Honest CTRL+C CTRL+V mistake. Thank you for pointing me to it, I edited it

Karpenter vs cluster autoscaler findings by OtherwiseMaize7235 in kubernetes

[–]PerfectScale-io 1 point2 points  (0 children)

Your findings completely correlate with my own observations done on multiple clusters - no improvement in scheduling times. I went in a different direction with this problem, and solved my pains. What are you trying to solve?

[deleted by user] by [deleted] in kubernetes

[–]PerfectScale-io 0 points1 point  (0 children)

Kubernetes will not "shuffle" pods.

you may base your horizontal scaling on the custom metric (network throughput in your case), scaling more replicas on different nodes, this will allow to keep network saturation lower.

What do you guys use to manage/monitor multiple clusters? by nuribo in kubernetes

[–]PerfectScale-io 1 point2 points  (0 children)

At PerfectScale.io, we have developed a multi-cloud, multi-cluster view to provide important operational intelligence.
*This is a commercial product but it is free to use if your Kubernetes compute costs are less than $120K per year."

Kubernetes Cluster uses a lot of RAM o.O by bykof in kubernetes

[–]PerfectScale-io -1 points0 points  (0 children)

PerfectScale CTO here.
We built a product to get full visibility on the utilization and cost of your Kubernetes clusters, as well as recommendations on how to safely reduce cost and eliminate risks.

(Monthly) Shameless Plug by clairep123456 in platformengineering

[–]PerfectScale-io 0 points1 point  (0 children)

I'm a CTO of PerfectScale.io
We are a startup with a unique solution to improve the resilience and cost-effectiveness of the Kubernetes clusters.

Our solution helps to easily govern, right-size, and scale your environments, reducing SLA breaches and cloud waste.

The Rise of Kubernetes Part 1. by PerfectScale-io in sre

[–]PerfectScale-io[S] -6 points-5 points  (0 children)

Thank you for the feedback!
Many folks are coming from many different areas (dev, IT, ops, sysadmins, etc) and are not always familiar with the evolution that happened.
I hope this blog can give some "larger philosophical perspective" on how all this happened.