The Ingress-NGINX project is pausing accepting new features and spending the next season working on stability. While they’re doing that, if you are an Ingress-NGINX user, please fill out their survey and help decide what features to prioritize when they start up again.
Next Deadline: Exceptions Due July 25th
The first 1.25 Alpha is available. Built with Golang 1.18.3, it includes few of the features that will eventually be in 1.25.0.
Cherry-pick deadline for the next set of patch releases is July 8th, so if you’re OOO for the American holiday, get those PRs done now.
The venerable and often-frustrating “kubeconfig” file has served as the primary configuration mechanism for
kubectl for a long time. This has offered a lot of flexibility to users managing multiple clusters, with features like PATH-style lookup and file merging, but these features have also made it difficult to add user-centric preferences to
kubectl, detached from cluster configuration details. SIG-CLI is proposing a new file,
kuberc, which would contain only user preferences and nothing related to cluster data. Some initial proposed use cases include allowing user-configured aliases to abbreviate common commands and persistent overrides for the default value of a value such as making
kubectl apply use
--server-side=true unless overridden.
This KEP has been brewing for many years but 1.25 will hopefully see a renewed push with a more detailed plan. The overall idea is to expose
oneOf validation for custom resource types, for cases like volume configuration on pods where there’s many substructs and exactly one must be used. Currently this behavior can only be implemented with a validation webhook (or perhaps a CEL expression if you’re on the bleeding edge) but as it is an extremely common thing in Kubernetes schemas, it will be nice to have as a full OpenAPI validation feature.
reflect.Pointeris the new
--chunk-sizewith a selector returns the right number of pods
cert-dir, CoreDNS anti-affinity
Last 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.