Stay up-to-date on Kubernetes development in 15 minutes a week.
Please check how the linter is working against your PRs. Both pull-kubernetes-linter-hints
and pull-kubernetes-verify-strict-lint
running on submit. Right now the latter is non-blocking, but it will change, so please report any times you see it failing to #k8s-code-organization.
Test jobs have been switched to running only external cloud providers, since that’s the default. Check if this breaks your tests.
Contributor Summits:
Also, don’t forget to vote for Steering Committee
Next Deadline: Production Readiness Review Freeze, September 28th
The Call for Enhancements is out; time to decide what feature(s) you can realistically finish before Nov. 1.
Patch releases, including a Go version bump, are due out this week.
KEP-2681: Field status.hostIPs added for Pod
KEP-2681 adds the status.hostIPs
pod field, which coexists with the singular status.hostIP
field. It shows both IPv4 and IPv6 addresses for smoother migration during the dual-stack transition phase. This also lets Kubernetes distinguish between the HostIP that is in use (if any), and the list of IPs that are potentially available.
This KEP was created by Shiming Zhang and received the alpha
milestone in v1.28
.
kubectl help
can display plugin subcommands--bind-address
since it doesn’t do what you think it does, but just in case we’ll ignore obvious wrong addressesjob_sync_duration_seconds
to 1minGOTOOLCHAIN
envTest Cleanup: Mock tests for Windows Kube-proxy, WaitForPodsResponding, StorageClass endpoints, DRA test flake, golangci-lint, stop using framework.ExpectEqual, PodGC unit tests
SkipFilterSchemaForKubectlOpenAPIV2Validation
because it’s unused, and also way too longLast Week In Kubernetes Development (LWKD) is a product of multiple contributors participating in Kubernetes SIG Contributor Experience. All original content is licensed Creative Commons Share-Alike, although linked content and images may be differently licensed. LWKD does collect some information on readers, see our privacy notice for details.
You may contribute to LWKD by submitting pull requests or issues on the LWKD github repo.