This is the second weekly edition of this experiment to provide a weekly digest newsletter of activity in the OpenShift enhancements repository.
As a request to enhancement authors, please try to capture the area of your enhancement in the summary line. That will make it easier to determine what the enhancement is related to when seeing it in a list of 1-liner summaries either in this list, via email subjects, or when looking at the list of open PRs.
: (comments this week / total comments) summary
There were 8 Merged pull requests:
259: (3/5) Add Machine Config Support in NTO proposal.
This enhancement proposes adding the ability for admins to target
MachineConfigPools and create MachineConfigs through the Node Tuning
Operator. With this enhancement we can take another step towards
full support for tuned profiles that need `[bootloader]`
support on RHCOS.
This feature was actually implemented several months ago, but the enhancement was never merged. It was updated to reflect that it was already implemented and then merged this week.
356: (0/59) network: on premise Service load balancers
OpenShift does not currently support Services of type=LoadBalancer on
bare metal or other on premise infrastructure environments. This
enhancement proposes a way forward, which is to adopt MetalLB.
The document explores some high level requirements, discusses some
alternatives considered, and maps out how we would get to work on
this through technical due diligence, upstream community engagement,
and careful planning of OpenShift integration with a new operator.
There is not currently a target for when this would be fully
supported, as this is a proposed enhancement on a direction to take.
More extensive technical due diligence, development, and testing will
help define the roadmap over time.
394: (0/44) Discuss host network configuration interfaces
This change introduces a new enhancement that discusses host network
configuration. It is different from the typical enhancement in that
its goal is informational and to discuss what is already present in
this area. It also provides references to other related works in
progress.
I wrote this first for myself and propose it here in hopes that it
may help others. I find that this context is important and helpful to
understand when discussing or reviewing enhancements for a specific
feature related to host network configuration.
I imagine this as a living document that should get updated as key
improvements are made to how we manage host network configuration for
OpenShift.
455: (3/10) network: add port registry
This document isn't exactly an enhancement. Rather it captures host
ports, so developers know which ones they can use.
457: (1/3) Enhancment: Select logs By pod label
Add an input selector to the ClusterLogForwarder (CLF) to forward
application logs from pods identified by labels.
Kubernetes has two ways to identify pods: namespaces and labels. The
CLF already has an input selector for namespaces, this enhancement will
add a selector for labels.
393: (2/2) cleanup assisted installer bare metal validations enhancement 294: (0/0) ingress/logging-api: Update status to "implemented" 285: (1/1) host-level-openvswitch: tweaks, enhancements
There were 10 New pull requests:
460: (0/0) Add empty-requests-policy enhancement 461: (0/0) Add aws-elb-idle-timeout enhancement 462: (3/3) Add client-tls enhancement 463: (2/2) [WIP] Describing steps to support out-of-tree providers 464: (1/1) use 'share' instead of 'projectedResourceName' in csi driver yaml examples 465: (12/12) Insights operator up to date gathering
This one generated the most comments on a new enhancement this week. The enhancement proposes a specific method to decouple the Insights Operator from OpenShift releases, using examples of a drawn out backport process as an example for why this is desirable. The discussion has highlighted that becoming an OLM operator that could be installed by default could be a more general solution to the problem raised, though this would take significant effort to accomplish. Ongoing improvements to the backport process and timeline could also reduce the pressure that led to the proposal.
466: (3/3) [WIP] Enhancement: Internationalization for console 467: (3/3) [WIP] Add MCO Flattened Ignition proposal 468: (5/5) Add dedicated instances proposal 469: (3/3) enhancement: console user settings
There was 1 Closed pull request:
287: (0/9) Ingress proposal: path rewriting
The following PRs received the highest number of comments in the last week:
429: (29/29) Enforce label scheme 448: (19/41) Proposal to enable JSON data processing 363: (17/73) Enhancement for adding upgrade preflight checks for operators 399: (17/55) [machine-config-operator/baremetal] MCO declarative network configuration 423: (17/24) Implement OpenStack Cloud Controller Manager support
That's it for this week.
Thanks for reading,
Russell Bryant Doug Hellmann