Kubernetes Kubelet Env File Parser Violates KEP-3721 on Duplicate Keys
Is it fixed? Not yet.
Ongoing since Nov 8, 13:51 UTC. First reported Nov 8, 13:51 UTC.
What happened
When an environment file defines the same variable multiple times, the kubelet's Env file parser assigns the first value instead of the last value. This behavior directly contradicts KEP-3721, which specifies that the last occurrence should take precedence and override previous values.
What caused it?
ParseEnv in pkg/kubelet/util/env/env_util.go immediately returns upon encountering the first instance of a key rather than continuing to process subsequent definitions.
Source: github.com
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
Env file parser uses the first definition of a duplicated key, KEP-3721 says the last one wins
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportEnv file parser uses the first definition of a duplicated key, KEP-3721 says the last one wins(opens GitHub issue in a new tab)
What happened? When an env file defines the same variable more than once, a fileKeyRef to that variable gets the first value. ParseEnv in pkg/kubelet/util/env/env_util.go returns as soon as it finds the key. KEP-3721 says the opposite under "Duplicate Names": "If an environment variable is defined multiple times in the file, the last occurrence takes precedence and overrides any previous values." The kubelet already resolves a duplicated name in a container's env list the same way, the last…
by imusmanmalik 0upvotes 1comments
FAQ
What happened in the Kubernetes issue?
When an environment file defines the same variable multiple times, the kubelet's Env file parser assigns the first value instead of the last value. This behavior directly contradicts KEP-3721, which specifies that the last occurrence should take precedence and override previous values.
What is affected by the Kubernetes issue?
Kubernetes.
When did the Kubernetes issue start and end?
It started Nov 8, 13:51 UTC and is still ongoing (10 d 14 h so far). This page updates as it develops.
How do I get alerts for Kubernetes?
Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.