$ the-wire · showcase
kubectl explain gains shell completion, kubelet threads real contexts
By RepoJournal · Filed · About Kubernetes · Composed from the cited sources · methodology
13 people shipped this
Kubernetes Publisher
@k8s-publishing-bot
1 cited
Oscar Wieman
@oscrx
1 cited
bart0sh
@bart0sh
1 cited
toVersus
@toVersus
1 cited
antcybersec
@antcybersec
1 cited
KashishV999
@KashishV999
hashicorp
@Kavyanjana
kubernetes-prow[bot]
@kubernetes-prow[bot]
mattcary
@mattcary
Nathan Herz
@natherz97
upodroid
@upodroid
Yiqing Wang
@YQ-Wang
amirialy
@amirialy
A cleanup-heavy day in kubernetes/kubernetes: kubectl explain completes resource fields on tab, the kubelet stops passing context.TODO(), and the apiserver stops building ServiceAccount storage twice.
kubectl explain: add auto completion (#140058) kubernetes/kubernetes
kubectl explain now completes resource types and fields at the prompt. The implementation reuses completion.CompGetResourceList rather than duplicating apiresources listing logic and depends on genericclioptions.RESTClientGetter instead of cmdutil.Factory.
kubelet: propagate context through Cache and GeneratePodStatus kubernetes/kubernetes
container.Cache.Get and GetNewerThan, plus Runtime.GeneratePodStatus, take a context.Context that is threaded through kubelet, pod_workers, PLEG, and the kuberuntime manager instead of context.TODO() and klog.TODO(); tests obtain contexts via ktesting.Init. The change is why request cancellation and klog values now reach those call sites.
Do not inherit probe state from a replaced container kubernetes/kubernetes
A container restart no longer inherits probe state from the container it replaced, closing the path where a stale probe result described the old process.
apiserver: build the pod-aware ServiceAccount storage exactly once kubernetes/kubernetes
When ServiceAccountIssuer is configured, GenericConfig.NewRESTStorage built a generic serviceaccounts backend that legacyProvider.NewRESTStorage immediately replaced and Destroy()'d, leaving two etcd watch caches and duplicate LIST work against etcd. The pod-aware storage is now constructed once.
Merge pull request #141493 from weizhoublue/fix-resolver-latency-metric-registration kubernetes/component-base
The resolverLatency metric in component-base is registered with legacyregistry, so consumers scraping the legacy endpoint see client-side resolver latency. Publishing and CI followed along: k8s.io added CoreWeave to the private distributors list and staged registries for sig-testing, generate.sh now only appends new image tags and never rewrites old ones, test-infra added Kueue MultiKueue perfo...
