Efficient node scaling is critical for making cloud native cost effective. #Karpenter is a key step to making scaling more optimized and dynamic in #Kubernetes and we are happy to announce the AKS Karpenter Provider https://t.co/PPiXUMAhiT
#kubecon
Kudos to the AWS team for starting this innovative project. We look forward to continued partnership on it under the SIG-Autoscaling umbrella.
Nathan Taber, Head of Product - EKS announcing donation of Karpenter project to SIG-Autoscaling in Kubernetes during the "Reduce Reuse Recycle" keynote!
#kubernetes#karpenter@kubernetesio@CloudNativeFdn
Excited to share AWS's proposal for Karpenter to join the Kubernetes organization as a SIG Autoscaling subproject. Interested in open governance for Karpenter? We want to hear from you! https://t.co/TXYsEYZ2J4
@achetronic@micahhausler@maria_fibonacci Sad to see this takeaway, given the team's efforts to make things friendly for other providers. Vendor neutrality has been a core design principle from the beginning of the project.
I'd love to dig in on the details on Slack or at our community meetings https://t.co/jCD5lA35Vq
I gave a talk at Kubecon EU in 2021 that discussed a design for complementary optimization loops for node Provisioning and Consolidation. I spent a year clarifying to users that it our vision, but not yet a reality. Now it's finally here! https://t.co/x9dI96j7zC
@jaypipes @VishnuDevaKR Couldn't help myself from grinning maniacally reading this glowing review. No better feeling than building something that people love.
@mattomata@ImJasonH@ahmetb Knative pkg's webhook reconciler is easily it's best feature. Honorable mention for apierrs, ptr, and conditions.
So good that it makes up for lack of versioned releases, no documentation, import conflicts with controllerruntime, and feeling I'm relying on a deprecated package
@mattomata Not the I'm aware of -- it's pain for Karpenter, Loadbalancer controller, etc. Cluster name introspection is challenging since name isn't an upstream concept, but is used broadly for resource discovery. What's your execution context? In Cluster Operator? Deployment pipeline?
I’m decided move our EKS clusters to Karpenter from Cluster Autoscaler after @rothgar’s Karpenter demo at AWS Community Day Turkey. We have been using Karpenter at 7 EKS cluster at the moment and It works like a charm! Thanks #AWS for such an awesome scaling solution!
Have you been wondering how to continuously train and deploy your models? This post describes how we solved this problem 👏 without forcing our data scientists to give up @ProjectJupyter 👏 and still using common #devops patterns like #gitops.
https://t.co/Wu4uZEBlhp
#mlops
KFServing is now 0.2! @ellisbigelow & Dan Sun speaking about how it's being used at @bloomberg for production-grade ML model serving. #KubeCon#kubeflow
We've released Kubeflow 0.7, with beta functionality for many components in preparation for Kubeflow 1.0 & exciting additions like #kfserving 0.2. This was a huge group effort. Thanks to all who contributed! https://t.co/WGKtyy3r4V