---
# System prepended metadata

title: catalogd discussion collection

---

# catalogd discussion collection


Trying to gather all the various threads where the 'why catalogd' RFC exploded, and then track all the pieces. 

- 08May2023 [why catalogd](https://redhat-internal.slack.com/archives/GHMALGJV6/p1683569635336859]) rh-slack/#team-operator-fw  
- 09May2023 [FBC read benchmarks](https://kubernetes.slack.com/archives/C0181L6JYQ2/p1683647766833719) (starts independent-ish and then collides)
- 10May2023 [RFC-formatted why-RFC](https://redhat-internal.slack.com/archives/GHMALGJV6/p1683758522797459) rh-slack/#team-operator-fw (also [here](https://kubernetes.slack.com/archives/C0181L6JYQ2/p1683758836151289) with no discussion)
- 10May2023 [reproducible installations using Operator API](https://kubernetes.slack.com/archives/C0181L6JYQ2/p1683727647910179) (dovetails strongly with the ongoing discussion)
- 11May2023 [FBC read optimizations](https://kubernetes.slack.com/archives/C0181L6JYQ2/p1683840778194409) (semi-tangential, but in blast radius)


