Beyond Kubernetes: Serverless Execution Models for Variable Workloads, with Marc Campora

https://ku.bz/5gMTkzLhV

Marc Campora, a systems consultant with experience in high-throughput platforms, shares his analysis of a real customer deployment with 500+ microservices. He breaks down the cost implications, technical constraints, and operational trade-offs between Kubernetes containers and AWS Lambda functions based on actual production data and migration assessments.

You will learn:

Cost analysis frameworks for comparing Lambda vs Kubernetes across different traffic patterns, including specific examples of 3x savings potential and the 80/20 rule for service utilization

Migration complexity factors when moving existing microservices to Lambda, including cold start issues, runtime model changes, and why it's often a complete rewrite rather than a simple port

Decision criteria for choosing between platforms based on traffic consistency, computational requirements, and operational overhead tolerance

Sponsor

This episode is sponsored by Learnk8s — get started on your Kubernetes journey through comprehensive online, in-person or remote training.

More info

Find all the links and info for this episode here: https://ku.bz/5gMTkzLhV

Interested in sponsoring an episode? Learn more.

via KubeFM https://kube.fm

June 17, 2025 at 06:00AM

Kubernetes AI: The Good, The Bad, and The Disappointing (kubectl-ai)

Discover how kubectl-ai, an AI agent specialized for Kubernetes cluster management, can streamline your workflow. This video explores its capabilities, limitations, and potential impact on DevOps practices. Learn how kubectl-ai compares to other AI tools and whether it's the right fit for your Kubernetes management needs.

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Sponsor: UpCloud 🔗 https://signup.upcloud.com/?promo=devopstoolkit That link gives 50€ free credits, with an extended trial of 30 days. ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

Kubernetes #AI #kubectl-ai

▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬ If you are interested in sponsoring this channel, please visit https://devopstoolkit.live/sponsor for more information. Alternatively, feel free to contact me over Twitter or LinkedIn (see below).

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬ ➡ BlueSky: https://vfarcic.bsky.social ➡ LinkedIn: https://www.linkedin.com/in/viktorfarcic/

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬ 🎤 Podcast: https://www.devopsparadox.com/ 💬 Live streams: https://www.youtube.com/c/DevOpsParadox

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬ 00:00 Kubernetes AI Intro 01:05 UpCloud (sponsor) 02:27 Finding and Fixing Issues with Kubernetes AI 06:40 Observability with Kubernetes AI 07:27 Create Resources with Kubernetes AI 11:39 Memory and Model Context Protocol (MCP) with Kubernetes AI 14:19 Pros and Cons

via YouTube https://www.youtube.com/watch?v=gNpCDKH0BTA

Changes to Kubernetes Slack

https://kubernetes.io/blog/2025/06/16/changes-to-kubernetes-slack/

Kubernetes Slack will lose its special status and will be changing into a standard free Slack on June 20. Sometime later this year, our community will likely move to a new platform. If you are responsible for a channel or private channel, or a member of a User Group, you will need to take some actions as soon as you can.

For the last decade, Slack has supported our project with a free customized enterprise account. They have let us know that they can no longer do so, particularly since our Slack is one of the largest and more active ones on the platform. As such, they will be downgrading it to a standard free Slack while we decide on, and implement, other options.

On Friday, June 20, we will be subject to the feature limitations of free Slack. The primary ones which will affect us will be only retaining 90 days of history, and having to disable several apps and workflows which we are currently using. The Slack Admin team will do their best to manage these limitations.

Responsible channel owners, members of private channels, and members of User Groups should take some actions to prepare for the upgrade and preserve information as soon as possible.

The CNCF Projects Staff have proposed that our community look at migrating to Discord. Because of existing issues where we have been pushing the limits of Slack, they have already explored what a Kubernetes Discord would look like. Discord would allow us to implement new tools and integrations which would help the community, such as GitHub group membership synchronization. The Steering Committee will discuss and decide on our future platform.

Please see our FAQ, and check the kubernetes-dev mailing list and the #announcements channel for further news. If you have specific feedback on our Slack status join the discussion on GitHub.

via Kubernetes Blog https://kubernetes.io/

June 15, 2025 at 08:00PM

Blog: Changes to Kubernetes Slack

https://www.kubernetes.dev/blog/2025/06/16/changes-to-kubernetes-slack-2025/

Kubernetes Slack will lose its special status and will be changing into a standard free Slack on June 20. Sometime later this year, our community will likely move to a new platform. If you are responsible for a channel or private channel, or a member of a User Group, you will need to take some actions as soon as you can.

For the last decade, Slack has supported our project with a free customized enterprise account. They have let us know that they can no longer do so, particularly since our Slack is one of the largest and more active ones on the platform. As such, they will be downgrading it to a standard free Slack while we decide on, and implement, other options.

On Friday, June 20, we will be subject to the [feature limitations of free Slack] https://slack.com/help/articles/27204752526611-Feature-limitations-on-the-free-version-of-Slack. The primary ones which will affect us will be only retaining 90 days of history, and having to disable several apps and workflows which we are currently using. The Slack Admin team will do their best to manage these limitations.

Responsible channel owners, members of private channels, and members of User Groups should take some actions to prepare for the upgrade and preserve information as soon as possible.

The CNCF Projects Staff have proposed that our community look at migrating to Discord. Because of existing issues where we have been pushing the limits of Slack, they have already explored what a Kubernetes Discord would look like. Discord would allow us to implement new tools and integrations which would help the community, such as GitHub group membership synchronization. The Steering Committee will discuss and decide on our future platform.

Please see our FAQ, and check the kubernetes-dev mailing list and the #announcements channel for further news. If you have specific feedback on our Slack status join the discussion on GitHub.

via Kubernetes Contributors – Contributor Blog https://www.kubernetes.dev/blog/

June 15, 2025 at 08:00PM

Week Ending June 8, 2025

https://lwkd.info/2025/20250611

Developer News

The next New Contributor Orientations will be held June 17th. If your SIG/WG/team has any help wanted opportunities to share, please let Mario know in #chairs-and-techleads.

The Elections Subproject is looking for another election officer for the 2025 Steering Election. Please review the role requirements, and express your interest.

Kubecon NA: The CFP for Maintainer Track talks and Project Kiosks is open and closes on July 7th. The CFP for the Maintainer Summit closes on July 20th.

Release Schedule

Next Deadline: PRR Freeze, June 12

Once you get done putting info in your KEPs for production readiness, you’ll be ready for the Enhancements Freeze 8 days later. Now’s the time to decide whether your enhancement is tracked for 1.34 or not.

Patch releases for June have been delayed until next week, as has the 1.34a1 release.

Featured PRs

131632: feat: Allow leases to have custom labels set when a new holder takes the lease

This PR allows users to set custom labels on LeaseLock resources when a new holder acquires the lease; users can now track which node holds the lease, thus improving observability for components using leader election.

KEP of the Week

KEP 3015: PreferSameZone and PreferSameNode Traffic Distribution

This enhancement deprecated the PreferClose Pod Topology Spread Constraints type and replaced it with PreferSameZone as a new name for the old behaviour. The KEP also added a new value PreferSameNode, which indicates that traffic for a service should preferentially be routed to endpoints on the same node as the client. This KEP made traffic distribution less ambiguous and delivers traffic to a local endpoint when possible. If the local endpoint is unavailable, the traffic is routed to a remote endpoint.

This KEP is tracked for beta in v1.34.

Other Merges

IsDNS1123SubdomainWithUnderscore function to return the correct error message

Fix for incorrect logging of insufficientResources in preemption

Support for API streaming from the List() method of the metadata client removed

Declarative validation to use named params and structured tags

Fix for unexpected delay of creating pods for newly created jobs

queue.FIFOs replaced with k8s.io/utils/buffer.Ring

kubeadm to consistently print an ‘error: ‘ prefix before errors

Promotions

ResilientWatchCacheInitialization to GA

Version Updates

gengo/v2 to latest

Subprojects and Dependency Updates

cloud-provider-openstack v1.33.0 adds OpenStack 2024.1, updates drivers, improves load balancer, fixes security and metadata, releases csi and controller charts v2.33.0

CoreDNS v1.12.2 adds multicluster, file fallthrough, forward proxy options, limits QUIC streams

etcd v3.6.1 replaces otelgrpc, adds member protections, fixes cluster removal and watcher race, validates discovery, builds with Go 1.23.10

grpc v1.73.0 enables Abseil sync on macOS/iOS, updates Protobuf, adds OpenSSL and disable sync flags

Shoutouts

Josh Berkus (@jberkus): Kudos to Carson Weeks (@Carson Weeks) and Ludo (@Ludo) for getting Elekto (the thing we use for Steering elections) to 97% unit test coverage. Yay!

via Last Week in Kubernetes Development https://lwkd.info/

June 11, 2025 at 07:59AM