Hypershift moving to 4.11 catalogs is perceiving high cpu & memory at catalog pod launch, with sustained memory use higher than expected.  The impact to hypershift is the potential density of their control plane with the need to handle spiking memory access. 

Team discussion can be found in slack:
https://coreos.slack.com/archives/GHMALGJV6/p1665668804923569

The original reporting issue can also be found in slack:
https://coreos.slack.com/archives/C01C8502FMM/p1665627729421399

Acceptance criteria:

• doc summarizing findings
• if we determine that pre-cached catalog pods aren't the answer, then creation of necessary stories to work toward a solution.