Skip to content

Latest commit

 

History

History
224 lines (160 loc) · 15.5 KB

2022-09-09.md

File metadata and controls

224 lines (160 loc) · 15.5 KB
Raw

This Week in Enhancements - 2022-09-09

Updates since 2022-09-02

Enhancements for Release Priorities

Prioritized New Changes

<PR ID>: (activity this week / total activity) summary

There was 1 Prioritized New pull request:

  • 1237: (26/26) microshift: Add MicroShift Default CSI Plugin proposal (copejon) (USHIFT-41)

    priority/important-soon

    This enhancement proposes the adoption of a default Container Storage Interface(CSI) Pluginfor Microshift. For more details on MicroShift, see the respective proposal. Kubernetes' CSI implementation provides a standardized model for exposing block and file storage systems to container workloads.

Prioritized Active Changes

<PR ID>: (activity this week / total activity) summary

There was 1 Prioritized Active pull request:

  • 1202: (1/228) storage: STOR-962: Update storage operators for HyperShift (jsafrane) (STOR-962)

    lgtm, priority/important-soon

    This enhancement describes how OCP storage components will run in HyperShift's managed control plane and in the guest cluster.

    The components currently are:

    • cluster-csi-snapshot-controller-operator and its operand, csi-snapshot-controller.
    • cluster-storage operator and its operand aws-ebs-csi-driver-operator and its operand AWS EBS CSI driver.
      • All other CSI driver operators + CSI drivers should follow the same approach, AWS EBS is just the first one to run its control plane in HyperShift's management cluster.

Other Enhancements

Other Merged Changes

<PR ID>: (activity this week / total activity) summary

There were 3 Other Merged pull requests:

  • 1179: (7/93) network: IP and Interface Selection (cybertron) (OPNET-134)

    As OpenShift is deployed in increasingly complex networking environments, we have gotten many requests for more control over which interface is used for the primary node IP. We provided a basic mechanism for this with KUBELET_NODEIP_HINT but as users have started to exercise that some significant limitations have come to light.

Other Merged Pull Requests Modifying Existing Documents

  • 1224: (2/9) dev-guide: Expand Boolean API convention example (JoelSpeed)
  • 1227: (3/8) update: expand the CVO featureset annotation to include other FeatureSets (deads2k)

Other New Changes

<PR ID>: (activity this week / total activity) summary

There were 5 Other New pull requests:

  • 1232: (2/2) installer: installer-aws: create edge compute pool for AWS Local Zones (mtulio) (RFE-2782)

    do-not-merge/work-in-progress

    The edge adoption is increasing and providers are launching many offerings that fill that area. AWS launched the Local Zones and the Wavelength zones to extend the VPC network to the metropolitan area from big centers, and for Radio Access Network, respectively, to allow application developers to to deliver low-latency applications at scale to the end users.

    As the resources in that locations were designed for specific workloads, and also have limited and more expensive cloud services, cluster operators should be able to create worker nodes on the edge networks on day zero operations.

    This enhancement introduces a new compute pool named edge, which will create MachineSets for each availability zone on the AWS Local Zones.

    The implementation was divided into three phases:

    • Phase 0: Research. Understand the Local Zones using the OKD/OCP, create use case and provides the documentation of installation a cluster in an existing VPC.
    • Phase 1: Install a cluster in user provided network introducing to the installer a new compute pool named edge. The MachineSet manifests will be created for each subnet provided on platform.aws.subnets for Local Zones. The Machine will be protected with taints to avoid running the normal platform workloads.
    • Phase 2: The installer should automate the network resource creation when the user provides zone names with type local-zone on the platform.aws.zones or compute[?name=="edge"].platform.aws.zones.

    Phases 1 and 2 are covered by this enhancement.

  • 1233: (5/5) hypershift: AUTH-311: hypershift: add an enhancement on trust separation (stlaz) (AUTH-311)

    lgtm

    At the time of writing the Hypershift is generating most of its certificates by using a single trust-all root CA. This enhancement describes how and why such a bundle should be split in order to assure workload portability between OpenShift-based products.

  • 1234: (5/5) cloud-integration: New "External" PlatformType addition proposal (lobziik) (OCPPLAN-9429) (OCPPLAN-8156)

    Historically, the k8s project contained plenty of code for handling integration with various cloud providers (AWS, GCP, vSphere). These pieces were developed and released along with the k8s as a part of a core, however, over time, the community concluded that this approach does not scale and manages well and should be changed. The community put a lot of energy into introducing the mechanism to allow cloud-providers and community members to build, develop, test and release provider-specific components independently from the Kubernetes core.

    Speaking about the Openshift integrations with cloud providers - for the moment, a lot of things are tended to be encoded in the Openshift codebase within API definitions, operators logic, and installer program code. This fact creates quite a lot of obstacles for RH partners and community members in their attempts to add new cloud providers to Openshift, as well as making RH engineering involvement quite necessary.

    Lately, there have been several initiatives around making Openshift more composable and flexible, for example Capabilites selection and Platform Operators are the significant steps towards this direction. However, despite having these powerful instruments, there is still necessary to land a code into the Openshift codebase for technical enablement of a new cloud provider, which might be hard or nearly impossible for external contributors.

    This EP describes adding a new special platform type, referred here as "External".

    Imagine some "MomAndPop Cloud" have created an infrastructure platform that resembles AWS but has its own API that is different than AWS. They would like to give their users the best OpenShift experience possible, but integrating their code into a Red Hat release is not possible for them. Using the "External" platform, capabilities, and platform operators, they can still deliver this functionality by creating their own Cloud Controller Managers, CSI drivers, network topology operators, Machine API controllers, and OpenShift configurations. This allows "MomAndPop Cloud" to provide the best OpenShift experience while also developing their components without the necessity of tying to Red Hat's internal processes or keeping a fork of the significant part of the Openshift code base.

    The new "External" platform type would serve as a signal when OpenShift is running on an infrastructure platform that will receive supplemental components from the infrastructure provider.

    "External" is different from our current platform types in that it will signal that the infrastructure is specifically not "None" or any of the known providers (e.g., AWS, GCP, etc.).

Other New Pull Requests Modifying Existing Documents

  • 1235: (18/18) update: Mention conditional update risks for cluster fleet evaluation (wking)
  • 1236: (3/3) update: enhancements/update/targeted-update-edge-blocking: Fix reqired-by-david typo (wking)

Other Active Changes

<PR ID>: (activity this week / total activity) summary

There were 12 Other Active pull requests:

  • 1191: (55/85) api-review: Apply user defined tags to all Azure resources created by OpenShift (bharath-b-rh) (OCPPLAN-8155) (CORS-2249)
  • 1206: (28/123) console: Enhancement doc to customize catalogs and sub-catalogs (lokanandaprabhu) (ODC-6695)
  • 1133: (25/60) general: Guidelines for the use of eBPF in OCP (danwinship)
  • 1158: (22/291) general: Ingress node firewall support using eBPF proposal (msherif1234) (SDN-2781)
  • 1205: (20/120) console: Created enhancement doc to customize perspectives (lokanandaprabhu) (ODC-5897)
  • 1213: (15/111) workload-partitioning: feat: add wide cluster configuration for workload partitioning (eggfoobar) (CNF-5562)
  • 1148: (13/78) 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)
  • 1212: (3/34) hypershift: Enhancment to support HostedClusterInfrastructure CRD (jnpacker) (ACM-1554)
  • 1198: (1/41) insights: VDPA enhancement (lmilleri)
  • 1217: (1/6) api-review: Apply user defined labels to all GCP resources created by OpenShift (bharath-b-rh) (OCPPLAN-8155) (CORS-2249)
  • 918: (1/248) installer: vsphere: add multiple datacenter and clusters (jcpowermac) (SPLAT-320)

Other Active Pull Requests Modifying Existing Documents

  • 1222: (2/9) dev-guide: Updates to workloads vs configuration API documentation (JoelSpeed)

Other Closed Changes

<PR ID>: (activity this week / total activity) summary

There were 2 Other Closed pull requests:

  • 1164: (2/36) general: Network Observability update for downstream operator and productization (jpinsonneau)

Other Closed Pull Requests Modifying Existing Documents

  • 1196: (2/14) console: Replace the 'Enabled' field with enum (jhadvig)

Idle (no comments for at least 7 days) Changes

<PR ID>: (activity this week / total activity) summary

There were 10 Idle (no comments for at least 7 days) pull requests:

  • 745: (0/152) security: Security Profiles Operator integration in OpenShift (JAORMX)
  • 1064: (0/74) network: Add enhancement proposal for SDN live migration (pliurh) (SDN-2612)
  • 1126: (0/59) cluster-logging: Logs-based alerts (periklis) (LOG-2510)
  • 1134: (0/64) installer: adding gcp-ipi-shared-vpc (jstuever) (CORS-1774)
  • 1167: (0/136) installer: openstack: add the notion of Failure Domains in the installer (EmilienM) (OSASINFRA-2908)
  • 1177: (0/78) ingress: NE-954: LoadBalancer Allowed Source Ranges Enhancement Proposal (suleymanakbas91) (NE-555)
  • 1189: (0/88) installer: Installer: check operators for stability (patrickdillon)
  • 1204: (0/10) hypershift: Enhancement proposal for HyperShift on P/Z/A (jaypoulz)
  • 1229: (0/2) hypershift: PSAP-742: Enable node tuning of HyperShift hosted nodes via NTO (dagrayvid) (PSAP-742)

Idle (no comments for at least 7 days) Pull Requests Modifying Existing Documents

  • 1225: (0/37) storage: Add enhancement for topology configuration (gnufied)

With lifecycle/stale or lifecycle/rotten Changes

<PR ID>: (activity this week / total activity) summary

There were 4 With lifecycle/stale or lifecycle/rotten pull requests:

  • 1106: (2/29) storage: OpenStack Cinder CSI Driver Operator Configurability (stephenfin) (OSASINFRA-2857)
  • 1181: (1/13) baremetal: Add enhacement for setting bootstrap kubelet ip (tsorya) (MGMT-11102)

With lifecycle/stale or lifecycle/rotten Pull Requests Modifying Existing Documents

  • 1188: (1/6) general: Update mount-namespace-hiding implementation plan to be environment-only (lack) (CNF-5326)
  • 1208: (1/5) release: Update revert instructions and link to TRT playbook (stbenjam) (edit)