Customer Problem

Memory/RAM usage is something that every Operator has to deal with. The defaults in controller-runtime or client-go can lead to high memory consumption because a lot of data is cached.

A telco architect/customer has a distributed radio access network (D-RAN) that consists of a large fleet of limited resource services that should run a fully supported single-node OCP deployment.

There is a set of (Red Hat/ISVs) Operators that they want to run on all of these in a reduced footprint.

Epic Goal

SDK team can look into to determine what options are available to help Operators reduce RAM consumption across the board.

Why is this important?

• Some bare metal edge customers, especially in the telco market, want to use kubernetes at physically remote sites with minimal hardware.

• Help Red Hat and partner Operators to reach edge customers/telcom/single node market.

Scenarios

1. As a SDK user, I want to have a more efficient way to control/filter resources that need to be cached for my Operator.

Acceptance Criteria

• SDK team can look into to determine what options are available and if there is potential something SDK can do to help reduce RAM consumption across the board.
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

• Controller-runtime:
  • https://github.com/kubernetes-sigs/controller-runtime/blob/master/designs/use-selectors-at-cache.md
  • https://github.com/kubernetes-sigs/controller-runtime/pull/1435

Previous Work (Optional):

1. Slack discussions

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>