SIG Autoscaling Bi-Weekly Karpenter Working Group for 20250519
Source: YouTube · Kubernetes · published May 19, 2025 · 23:50
The meeting reviews and categorizes open issues in AWS Carpenter, focusing on triage, information gathering, and assigning ownership with clear next steps. Key issues are evaluated for resolution, investigation, or deferral.
Key Takeaways:
• A heuristic to adjust node disk size based on CPU usage is under review and has been moved to "needs information" for further RFC discussion 1:10.
• A duplicate node claim issue in cover cluster policies is assigned to Jagisha for tracking and detailed investigation summary 2:08.
• A problem with taints and pod scheduling during node provisioning causes cost increases and node thrashing, specifically involving the "unregistered no execute" taint 2:47.
• An issue with not removing empty nodes after capacity stabilizes is marked as "needs investigation" pending feedback 5:53.
• A feature request for discounts over 40% is deemed acceptable as-is, with no immediate action needed 9:32.
• A high CPU usage issue post-upgrade is resolved with triage closure and noted as solved 13:41.
The team concludes that most issues require further investigation or documentation, and recommends a follow-up in the Carpenter Dev channel to prioritize work.
Sources:
Generate CPE Credits
Generate a professional CPE document from this video's transcript.
Estimated credit: 0.5 CPE hours
Estimate uses the video runtime (1 hour ≈ 1 CPE, rounded to the nearest 0.5, minimum 0.5, maximum 2.0). The final amount can be lower after review, never higher.
Topic: Cloud Security. Commonly maps to: Security Architecture and Engineering, Communication and Network Security. Exact CISSP domains are assigned during generation.
Free account. One generation at a time, with a daily limit.
CPEBuddy is independent and not affiliated with or endorsed by ISC2, ISACA, or any certification body. Exports are formatted for common CPE submissions; acceptance is at your certification body's discretion.
Transcript Preview
First 800 characters of the transcript
Okay. Hi everyone. This is the AWS carpenter provider triage uh meeting for any issues that are new as well as reviewing issues that uh we have marked as needs information and just generally going through and either discussing or trying to assign out a little bit of work. So this is an issue from a few weeks ago and uh if I remember correctly they basically want to introduce a um heristic that adjusts the node disk size based on CPUs for the nodes. uh while they say that there were other providers I believe or not necessarily providers but other offerings out there um that will do this kind of heristic. I've asked them for a proper RFC just to make sure that it's something that makes sense and has a bunch of considerations or other approaches that we might want to do. So I don't think that…