BrevFeed
Sign in
← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Kubernetes v1.37 Deprecates kubectl run --filename, Fixes Static Pod API References, and Phases Out kube-proxy IPVS Mode

🔄 Updated 1d ago
Aggregated by BrevFeed releases · updated 15d ago
🔖 Save
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • kubectl run --filename flag is deprecated.
  • Static Pods can no longer reference Secrets or ConfigMaps directly.
  • kube-proxy IPVS mode is being deprecated, with removal by v1.43.
  • cgroup v1 support is being phased out.

kubectl run --filename Deprecation

The `--filename` (or `-f`) flag for `kubectl run` is being deprecated. This flag was problematic because the generated pod was always constructed solely from command-line arguments like `NAME` and `--image`, making the filename redundant.

Static Pod API Reference Fix

A bug that allowed static pods to reference Secrets or ConfigMaps via fields like `configMapRef` or `secretRef` has been fixed. Static Pods are not created through the API server, so direct API resource references were never intended. As of v1.37, these references are strictly prohibited, and the `PreventStaticPodAPIReferences` feature gate has been removed.

kube-proxy IPVS Mode Deprecation

Support for `kube-proxy` in IPVS mode is being phased out. While IPVS mode was introduced in v1.8 to address `iptables` performance issues, it still relies on `iptables` for full Kubernetes Service implementation. Clusters running `kube-proxy` in IPVS mode will now log a deprecation warning on startup.

The deprecation timeline indicates that IPVS mode will be disabled by default in v1.40 and entirely removed by v1.43. This change is documented in KEP-5495.

cgroup v1 Phasing Out

Support for the legacy cgroup v1 is being officially phased out. Modern Linux distributions and container runtimes now default to cgroup v2. Since the v1.35 release, the `failCgroupV1` setting has defaulted to `true`, meaning `kubelet` will fail to initialize on nodes still using cgroup v1.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

Keep reading

dev Kubernetes Extends Reach to Desktop Infrastructure, Highlighting Database Management Challenges 19h ago cloud Amazon EKS Introduces Kubernetes Version Rollback and Extended Support 14d ago security HashiCorp Releases Public Beta of Vault Kubernetes Key Management for Encryption at Rest 12d ago releases Gateway API v1.6.0 Graduates TCPRoute and UDPRoute to Standard, Expands Layer 4 Routing 12d ago dev JDK 28 Targets New Features, JDK 27 Release Candidate Delayed 5d ago

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~7 min · 6 stories · Aug 15

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Primary sources

GitHub kubernetes/kubernetes GitHub kubernetes/enhancements GitHub kubernetes/sig-release GitHub kubernetes/website CVE CVE-2025-19749.8 CRITICAL CVE CVE-2019-57368.6 HIGH

Reporting from

Kubernetes Blog — Kubernetes v1.37 Sneak Peek 15d ago →

Kubernetes v1.37 will deprecate the `--filename` flag for `kubectl run`, fix a bug allowing static pods to reference API resources, and begin phasing out `kube-proxy` IPVS mode. These changes aim to improve consistency, security, and align with modern Linux cgroup standards.