Cloud Native

Kubernetes v1.37 Deprecations to Act On Now | Dipesh Rawat, CNCF | TFiR

0

Three components that many production Kubernetes clusters still depend on are deprecated in v1.37: the --filename flag for kubectl run, kube-proxy IPVS mode, and KubeDNS. Deprecation warnings are already printing in logs. Security updates for KubeDNS stop with this cycle. Teams that delay migration are accumulating risk that will surface as a forced, time-pressured change when removal lands.

In this interview on TFiR, Dipesh Rawat, Kubernetes v1.37 Release Lead at CNCF, walks through each deprecation, the rationale behind it, and exactly what to migrate to before these components are removed.

Guest: Dipesh Rawat, Kubernetes v1.37 Release Lead at CNCF
Show: TFiR

Here is what every platform engineer and cluster operator needs to know.

Technical Deep Dive

Q: What is being deprecated in Kubernetes v1.37 that cluster operators must act on?

Dipesh Rawat, Kubernetes v1.37 Release Lead at CNCF, identifies three deprecations: the --filename / -f flag for kubectl run, kube-proxy IPVS mode, and KubeDNS. None are immediate removals, but deprecation warnings are now active and migration should begin before the removals land in a future release. Rawat emphasizes that these decisions were deliberate project-level choices to align Kubernetes with modern infrastructure primitives.

“We have a few deprecations that were part of the release.”

Dipesh Rawat, Kubernetes v1.37 Release Lead, CNCF

Q: Why is the -f flag being removed from kubectl run in Kubernetes v1.37?

The --filename / -f flag for kubectl run was never intended to apply declarative YAML specs. Its correct use case was running pods or resources directly from command-line flags, not from a file. Rawat explains the project drilled down to make this separation explicit: kubectl apply and kubectl create are the correct commands for declarative workflows. The flag has been removed to eliminate this long-standing source of user confusion.

“kubectl run was meant to run pods or resources directly from the flag. It was never meant to run a declarative spec.”

Dipesh Rawat, Kubernetes v1.37 Release Lead, CNCF

Q: Why is kube-proxy IPVS mode being deprecated and what should teams migrate to?

IPVS mode was originally added to kube-proxy for performance advantages over iptables. With nftables now available and maturing in Kubernetes, the project has decided to retire IPVS mode. Rawat notes that clusters currently running kube-proxy in IPVS mode will see a deprecation warning in logs. Teams can run a specific command to check which mode their kube-proxy is operating in and should begin planning a migration to nftables now.

“Currently if you start kube-proxy in IPVS mode, in the logs you will get a message that it is going to be deprecated in future releases.”

Dipesh Rawat, Kubernetes v1.37 Release Lead, CNCF

Q: Why is KubeDNS being deprecated and what does it mean for clusters still running it?

CoreDNS has been the default DNS provider in Kubernetes clusters for years, making KubeDNS redundant. Rawat explains the project has decided to retire KubeDNS entirely: it will stop receiving security updates in future releases. Any cluster still running KubeDNS is therefore accumulating unpatched security exposure over time. Migration to CoreDNS is the required path, and Rawat notes it brings concrete feature gains rather than being a neutral swap.

“KubeDNS is going to stop receiving security updates in the future. So if for any reason you are running KubeDNS, please try to migrate to newer CoreDNS.”

Dipesh Rawat, Kubernetes v1.37 Release Lead, CNCF

Q: What features does CoreDNS provide that KubeDNS does not?

Rawat specifically calls out two capabilities available in CoreDNS that KubeDNS does not support: endpoint slices and in-place memory QoS. Endpoint slices improve DNS scalability and performance in large clusters. In-place memory QoS allows finer-grained resource management without pod restarts. Both are aligned with the broader Kubernetes v1.37 feature direction and represent tangible operational improvements for teams that complete the migration.

“It will give you access to newer features such as endpoint slices and in-place memory QoS. So it’s a win win for everybody.”

Dipesh Rawat, Kubernetes v1.37 Release Lead, CNCF

Resources & Documentation

***

👇 Click to Read Full Raw Transcript

Swapnil Bhartiya: Now as much as we are excited about all these new features, are there anything that are being deprecated in this release that user should be aware of?

Dipesh Rawat: We have a few deprecations that were part of the release, so first I would go with a quick one. So in kubectl, everyone’s favorite cli, we have deprecated the minus F or minus minus file name flag for kubectl run. So traditionally kubectl run was meant to run Pokemon pods or resources directly from the flag. It was never meant to run a declarative spec that you gave it a YAML and it is going to run so that for that you use create and apply. So we have drilled down and made it more obvious that F or file name is not should not be used by kubectl run command. So that flag has been removed for kube-proxy. IPVS mode is going to be deprecated in the future releases to IPVS mode. Was we originally added for performance for IP tables and stuff. Now we have NF tables and we have got new features that are present with that. So we have decided to retire that mode. So currently if you start kube-proxy in IPVS mode in the logs you will get a message that it is going to be deprecated in the future releases. As said in the release announcement it is going to be removed. Again, it’s not an immediate removal. We are giving you the deprecated warning according to a so please try to migrate. If you are running kube-proxy in IPVS mode in your cluster there is a particular command that you can use to identify what mode your kube-proxy is running. The other deprecation is Kubedns is being deprecated. So for a long time CoreDNS has been the default DNS provider in our cluster. So Kubedns we have decided as a project today to retire that project. So it is going to stop receiving security updates in the future. So if for any reason you are running kubedns please try to migrate to newer core DNS. It will give you access to newer features such as endpoint slices and in place memory QoS. So it’s a win win for everybody.

GitHub App Keys That Never Expire | Gaetan Ferry, GitGuardian | TFiR

Previous article

Operational AI for Buildings: From Data to Action | OP Ravi, Willow | TFiR

Next article