# OLM De-Scoping Plan Overview

This is Chris Johnson's (IBM) point of view and tracking of the next-generation OLM API plans as I see them.

Operator Lifecycle Manager is evolving to a new API that will separate out several concerns that are currently combined into an API that is largely incompatible with many of today's use cases:
- Tenancy
- Security
- Declarative provisioning

## Index of documents
There is no single API or issue to follow. This new API is a set of new features which are described here:

- [De-Scoping Plan hackmd](https://hackmd.io/wVfLKpxtSN-P0n07Kx4J8Q) - Start here
- [User Experience hackmd](https://hackmd.io/FdDket7MQmClYxHPxLk8Rw) - General flow
- [e2e Strawman hackmd](https://hackmd.io/@ecordell/rymiBziZO) - Describes RukPak, Deppy and Maestro
- [Simplified Operator API - OLM-1579](https://issues.redhat.com/browse/OLM-1579)
- [Old Enhancement Proposal](https://github.com/operator-framework/enhancements/blob/master/enhancements/simplify-olm-apis.md) - Describing the Operator API
- [RukPak hackmd](https://hackmd.io/nS8lS71uSmCTaPGfbWII_g) - Bundles
- [KuberPak](https://github.com/joelanford/kuberpak) - Bundle Prototype
- [Deppy](https://hackmd.io/sxT8wkBvTIy1n9C27Eo7SQ) - Dependency Management
- [Maestro hackmd](https://hackmd.io/mwY2A7V4RjOLbetL--Uk-w) - Authorization model
-