forked from openshift/enhancements
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request openshift#1178 from dhellmann/twie-2022-07-08
this-week: 2022-07-08
- Loading branch information
Showing
1 changed file
with
160 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,160 @@ | ||
# This Week in Enhancements - 2022-07-08 | ||
|
||
*Updates since 2022-07-01* | ||
|
||
|
||
## Enhancements | ||
|
||
### Merged Changes | ||
|
||
*<PR ID>: (activity this week / total activity) summary* | ||
|
||
There were 8 Merged pull requests: | ||
|
||
- [1166](https://github.com/openshift/enhancements/pull/1166): (6/6) hypershift: Add enhacement for hypershift networking (enxebre) ([OCPPLAN-5771](https://issues.redhat.com/browse/OCPPLAN-5771)) | ||
|
||
> This proposal fleshes out the details for the current networking solution for HyperShift form factor i.e. hosed control planes. | ||
- [1168](https://github.com/openshift/enhancements/pull/1168): (5/5) hypershift: Add monitoring enhacement for HyperShift (enxebre) ([OCPPLAN-5771](https://issues.redhat.com/browse/OCPPLAN-5771)) | ||
|
||
> This proposal fleshes out the details for the current monitoring solution for HyperShift form factor i.e. hosed control planes. | ||
> This includes which metrics to expose, how to expose them and approaches to collect them. | ||
|
||
#### Merged Pull Requests Modifying Existing Documents | ||
|
||
- [1149](https://github.com/openshift/enhancements/pull/1149): (8/27) api-review: [CFE-508] As a developer I want to update enhancement to support AWS user tag GA (TrilokGeer) | ||
- [1152](https://github.com/openshift/enhancements/pull/1152): (4/18) storage: Add enhancement change for disabling SC creation (gnufied) | ||
- [1157](https://github.com/openshift/enhancements/pull/1157): (16/46) windows-containers: [WINC] WICD Services CM retrieval & data constraints (saifshaikh48) | ||
- [1171](https://github.com/openshift/enhancements/pull/1171): (4/4) general: Hypershift networking: Add oauth server and detail socks5 proxy (alvaroaleman) ([OCPPLAN-5771](https://issues.redhat.com/browse/OCPPLAN-5771)) | ||
- [1173](https://github.com/openshift/enhancements/pull/1173): (7/7) installer: Document the steps to introduce a new optional capability (bparees) ([OCPPLAN-7589](https://issues.redhat.com/browse/OCPPLAN-7589)) | ||
- [1174](https://github.com/openshift/enhancements/pull/1174): (16/16) installer: enhancements/installer/component-selection: Suggest early annotation presubmits (wking) ([OCPPLAN-7589](https://issues.redhat.com/browse/OCPPLAN-7589)) | ||
|
||
### New Changes | ||
|
||
*<PR ID>: (activity this week / total activity) summary* | ||
|
||
There were 6 New pull requests: | ||
|
||
- [1167](https://github.com/openshift/enhancements/pull/1167): (20/20) installer: openstack: add the notion of Failure Domains in the installer (EmilienM) ([OSASINFRA-2908](https://issues.redhat.com/browse/OSASINFRA-2908)) | ||
|
||
> For organizations where service availability is a concern, networking architectures are usually more modern than what we can find in a traditional datacenter. | ||
> For example, the "Spine and Leaf" design is a recommended choice when deploying OpenStack at scale. | ||
> In this architecture, each leaf (lower-level access switch) is connected to multiple spines (upper-level core switch) in a full mesh. The latency becomes predictable, there is no more bottleneck and overall the resilience is improved. | ||
> Each leaf brings their own network fabrics that are usually using their own power units. Also each network fabric manages their its own Layer-2 domain, and therefore network subnets. Routing protocols are usually used so applications can communicate each other in the datacenter, since they don't live within the same domain anymore. | ||
> | ||
> In this enhancement, we would like to support the deployment of OpenShift into multiple subnets from day 1, using IPI. | ||
> To accomplish this, the OpenStack administrator will pre-create a Routed Provider Network and one or multiple subnets per leaf, which will be linked to an Availability Zone, here called Failure Domain for a better understanding. | ||
> Each Failure Domain will have its own network subnet and storage resources used by OpenShift. | ||
> This feature will remove the limitation that we have today in BYON (Bring your own network) which is the support of a single primary subnet for the machines on day 1. We want to be able to deploy the cluster across multiple subnets and storage sources, where each resource live in a given Failure Domain. | ||
- [1170](https://github.com/openshift/enhancements/pull/1170): (173/173) olm: Add a platform operators (phase 0) proposal (timflannagan) ([OLM-2232](https://issues.redhat.com/browse/OLM-2232)) ([OLM-2513](https://issues.redhat.com/browse/OLM-2513)) ([OLM-2605](https://issues.redhat.com/browse/OLM-2605)) | ||
|
||
`do-not-merge/work-in-progress` | ||
|
||
> The enhancement outlines a mechanism that enables support for the lifecycle of platform operators. A platform operator (PO) is an OLM-based cluster extension that can be installed during day 0 operations, and lifecycles with the cluster. This mechanism will ultimately be divided into phases, and this proposal covers the first phase in more detail. | ||
> | ||
> This first phase introduces a basic PO installation mechanism, and helps build the foundational layer for subsequent phases. Future phases may introduce a first-class PO management mechanism for the OLM component. | ||
- [1175](https://github.com/openshift/enhancements/pull/1175): (3/3) windows-containers: [WINC] WMCO: Update container runtime details (mansikulkarni96) | ||
|
||
> The intent of this enhancement is to allow a cluster administrator to add a | ||
> Windows compute node as a day 2 operation with a prescribed configuration to an | ||
> installer provisioned OpenShift 4.6 cluster and enable scheduling of Windows | ||
> workloads. The targeted platforms for 4.6 are vSphere, Azure and AWS. The | ||
> cluster has to be configured with Hybrid OVN networking. | ||
- [1176](https://github.com/openshift/enhancements/pull/1176): (2/2) installer: enhancements/installer/component-selection: Fix "capabilities" -> "capability's" typo (wking) ([OCPPLAN-7589](https://issues.redhat.com/browse/OCPPLAN-7589)) | ||
|
||
> This enhancement proposes a mechanism for cluster installers to exclude one or more optional components | ||
> (capabilities) for their installation which will determine which payload components are/are not installed | ||
> in their cluster. Core components are defined as the set of Second Level Operators managed by the Cluster | ||
> Version Operator which today cannot be disabled until after completing the install and editing a CVO | ||
> override, or editing the CVO overrides as part of rendering+editing manifests. In addition, using CVO | ||
> overrides put the cluster into an unsupported and un-upgradeable state, making it insufficient as a solution. | ||
> | ||
> The proposed UX is to make this a first class part of the install config api with the implementation | ||
> being arguments supplied to the CVO to filter out the user-selected manifests based on groupings called | ||
> capabilities. | ||
- [1177](https://github.com/openshift/enhancements/pull/1177): (2/2) ingress: NE-954: LoadBalancer Allowed Source Ranges Enhancement Proposal (suleymanakbas91) ([NE-555](https://issues.redhat.com/browse/NE-555)) | ||
|
||
`do-not-merge/work-in-progress` | ||
|
||
> This enhancement extends the IngressController API to allow the user to specify a | ||
> list of IP address ranges for an IngressController to which access to the LoadBalancer Service | ||
> should be restricted when `endpointPublishingStrategy` is `LoadBalancerService`. | ||
> By default, all source addresses are allowed (which is equivalent to | ||
> specifying "0.0.0.0/0"). Currently, the only way for the customers to limit this is by | ||
> setting `.Spec.LoadBalancerSourceRanges` field for the LoadBalancer Service | ||
> in front of the router in cloud environments. This is not desired as we prefer | ||
> the customers use the APIs and do not directly modify the managed resources. | ||
|
||
#### New Pull Requests Modifying Existing Documents | ||
|
||
- [1172](https://github.com/openshift/enhancements/pull/1172): (6/6) housekeeping: owners: Remove selansen (sebsoto) | ||
|
||
### Active Changes | ||
|
||
*<PR ID>: (activity this week / total activity) summary* | ||
|
||
There were 9 Active pull requests: | ||
|
||
- [1158](https://github.com/openshift/enhancements/pull/1158): (25/123) general: Ingress node firewall support using eBPF proposal (msherif1234) ([SDN-2781](https://issues.redhat.com/browse/SDN-2781)) | ||
- [1164](https://github.com/openshift/enhancements/pull/1164): (11/29) general: Network Observability update for downstream operator and productization (jpinsonneau) | ||
- [1163](https://github.com/openshift/enhancements/pull/1163): (6/26) installer: Installer: user-encrypted storage keys enhancement (patrickdillon) | ||
- [1148](https://github.com/openshift/enhancements/pull/1148): (5/21) installer: This proposal describes how we would add a new field to the install-config during installation to set the load balancer type in AWS either to NLB or ELB. (miheer) ([NE-942](https://issues.redhat.com/browse/NE-942)) | ||
- [1014](https://github.com/openshift/enhancements/pull/1014): (4/462) multi-arch: Heterogeneous architecture clusters (Prashanth684) ([RFE-2240](https://issues.redhat.com/browse/RFE-2240)) ([OCPPLAN-4577](https://issues.redhat.com/browse/OCPPLAN-4577)) | ||
- [1126](https://github.com/openshift/enhancements/pull/1126): (3/53) cluster-logging: Logs-based alerts (periklis) ([LOG-2510](https://issues.redhat.com/browse/LOG-2510)) | ||
- [1139](https://github.com/openshift/enhancements/pull/1139): (2/5) dns: NE-927: CoreDNS Cache Tuning Enhancement Proposal (brandisher) | ||
- [1106](https://github.com/openshift/enhancements/pull/1106): (2/25) storage: OpenStack Cinder CSI Driver Operator Configurability (stephenfin) ([OSASINFRA-2857](https://issues.redhat.com/browse/OSASINFRA-2857)) | ||
|
||
#### Active Pull Requests Modifying Existing Documents | ||
|
||
- [1159](https://github.com/openshift/enhancements/pull/1159): (1/7) dns: Bug 2088606: Update DNS-over-TLS proposal (brandisher) ([NE-703](https://issues.redhat.com/browse/NE-703)) | ||
|
||
### Closed Changes | ||
|
||
*<PR ID>: (activity this week / total activity) summary* | ||
|
||
There were 3 Closed pull requests: | ||
|
||
- [1131](https://github.com/openshift/enhancements/pull/1131): (2/22) .github: add a PR template for enhancements (kikisdeliveryservice) | ||
|
||
#### Closed Pull Requests Modifying Existing Documents | ||
|
||
- [1161](https://github.com/openshift/enhancements/pull/1161): (2/7) cluster-logging: NO-JIRA: Fix tab/space problems in document. (alanconway) | ||
- [1169](https://github.com/openshift/enhancements/pull/1169): (2/2) housekeeping: Add Cesar to owners file for ability to approve (enxebre) | ||
|
||
### Idle (no comments for at least 7 days) Changes | ||
|
||
*<PR ID>: (activity this week / total activity) summary* | ||
|
||
There were 9 Idle (no comments for at least 7 days) pull requests: | ||
|
||
- [745](https://github.com/openshift/enhancements/pull/745): (0/141) security: Security Profiles Operator integration in OpenShift (JAORMX) | ||
- [811](https://github.com/openshift/enhancements/pull/811): (0/92) network: Enhancement proposal for OVN secondary networks (maiqueb) | ||
- [918](https://github.com/openshift/enhancements/pull/918): (0/213) installer: vsphere: add multiple datacenter and clusters (jcpowermac) | ||
- [1064](https://github.com/openshift/enhancements/pull/1064): (0/70) network: Add enhancement proposal for SDN live migration (pliurh) ([SDN-2612](https://issues.redhat.com/browse/SDN-2612)) | ||
- [1121](https://github.com/openshift/enhancements/pull/1121): (0/6) general: Observability Query Language (preliminary draft, incomplete) (alanconway) | ||
- [1133](https://github.com/openshift/enhancements/pull/1133): (0/32) general: Guidelines for the use of eBPF in OCP (danwinship) | ||
- [1150](https://github.com/openshift/enhancements/pull/1150): (0/21) ocp-coreos-layering: User experience workflow in OCP CoreOS Layering model (sinnykumari) | ||
|
||
#### Idle (no comments for at least 7 days) Pull Requests Modifying Existing Documents | ||
|
||
- [1102](https://github.com/openshift/enhancements/pull/1102): (0/11) network: Dual stack VIPs: Add rules for openshift/api fields on upgrades (creydr) ([SDN-2213](https://issues.redhat.com/browse/SDN-2213)) | ||
- [1107](https://github.com/openshift/enhancements/pull/1107): (0/38) ingress: Update enhancement for aws-load-balancer-operator (thejasn) ([CFEPLAN-39](https://issues.redhat.com/browse/CFEPLAN-39)) | ||
|
||
### With lifecycle/stale or lifecycle/rotten Changes | ||
|
||
*<PR ID>: (activity this week / total activity) summary* | ||
|
||
There were 3 With lifecycle/stale or lifecycle/rotten pull requests: | ||
|
||
- [1134](https://github.com/openshift/enhancements/pull/1134): (1/56) installer: adding gcp-ipi-shared-vpc (jstuever) ([CORS-1774](https://issues.redhat.com/browse/CORS-1774)) | ||
|
||
#### With lifecycle/stale or lifecycle/rotten Pull Requests Modifying Existing Documents | ||
|
||
- [1129](https://github.com/openshift/enhancements/pull/1129): (6/32) general: Adding more priority labels (LalatenduMohanty) | ||
- [1138](https://github.com/openshift/enhancements/pull/1138): (1/18) etcd: Added several removing items else machine creation will fail (geliu2016) |