---
# System prepended metadata

title: Bundle Index Options

---

# Bundle Index Options

### Previous Discussions

* https://kubernetes.slack.com/archives/C038B7MF75M/p1655152627668319?thread_ts=1655136496.056889&cid=C038B7MF75M
    * tldr: follow a prometheus model and scrape catalogs (deppy entries) analogously to scraping metrics
### Proposal

 * Have a Package resource
 * Include channel and package metadata in it
 * Make Catalogs (versioned) RukPak bundles that apply and maintain Package resources

##### Why

* Top level API for users to query packages that are available or installed
* Gives declarative view/access to channels and their upgrade paths
* Gives clear visibility as to dependencies and constraints for bundles
* Removes need the package manager service
* Removes need for index API

##### Things to Consider

* Packages/Bundles can include chunky metada e.g. images, which can bloat the resource size
* MicroShift resource limitations: can this blow out server memory?
* 1MB etcd size limit
* What about the Operator API?

##### 4.11 Index Package/Bundle Count

| CatalogSource   | # Channels | # Packages  | # Bundles   |
| --------------- | ---------- | ----------- | ----------- |
| **Red Hat**     |            | 90          | 554         |
| **Certified**   |            | 92          | 197         |
| **Marketplace** |            | 37          | 66          |
| **Community**   |            | 165         | 1302        |
| **Total**       |            | 387         | 2119        |
