operator-controller
operator-controller copied to clipboard
operator-framework
Basic API dependency support - Use existing `olm.gvk.required` - Use discovery API to understand what is provided.
### Design Docs - [Brief: Constraints & pre-flight checks](https://docs.google.com/document/d/1XTqAVu_uSBs8reScQpyR5leesmp8f6CEYfwE2AptBW4/edit#heading=h.btd8kkom5km4) ### Task list - \
Define a way for the content author to specify what parameters are user-facing, along with a way to plumb them through from the ClusterExtension spec the templating engine Example use...
Show an aggregated healthy/unhealthy view of the resources applied to the cluster via an Extension. May show the first few details but don't show every unhealthy resource.
After #596 goes in, we can implement support for installing a bundle from a URL instead of resolving it from a catalog. To do this, we'll have a very strict...
- [x] #1751 - [x] #1752 - [x] #1753 - [x] #1750 - [x] #612 - [x] #613 - [x] #614
# Description - Refactors the types in the `internal/catalogmetadata` package to reduce the complexity of requiring all the OLM-isms to be conveyed through the single `Bundle` type. Updates all resolution...
This is issue is to allow the bundle resources remain in cluster, intentionally when the respective owner API is set of deletion. With respect to Extension API, that uses App...
Update the documentation to reflect the current development state of OLM 1.0. Content: - [ ] Remove "Why OLM v1?" in favor of the "OLM v1 Overview" introduced in #692...
