---
title: Platform Operators Wiki
author: timflannagan
---

## Overview

An initial attempt at a wiki for platform operators.

## Problem Statement

[See the phase 0 enhancement for more details](https://github.com/openshift/enhancements/blob/master/enhancements/olm/platform-operators.md#motivation).

## Stakeholders

- Ben Parees (Staff)
- Joe Lanford (Staff)
- Daniel Messer (PM)
- Trevor King (CVO)
- Alex Dellapenta / Michael Peter (Docs)
- Mike McCune (Cloud / Install Flexibility)
<!-- TODO: TE/PX/QE contacts -->

## Communication

- [Slack #tmp-platform-operators channel](https://coreos.slack.com/archives/C030W4V9BHN)
- [Upstream o/platform-operators github issues](https://github.com/openshift/platform-operators/issues)

## Roadmap

See the [platform operators roadmap hackmd](https://hackmd.io/MFwDuS_XS7quls3Q4ANKLw) for more information.

## FAQ

See the [platform operators FAQ hackmd](https://hackmd.io/pn-nrK_tRA6aaSDHQdkH7g) for more information.

## Where do I file bugs?

- [Bugs related to platform operators are filed on the OLM component](https://issues.redhat.com/browse/OCPBUGSM-28224?jql=project%20%3D%20OCPBUGSM%20AND%20component%20%3D%20OLM)
- Bugs related to the individual components are filed on their boards

## What's the current project status?

- Productized the rukpak OLM 1.x sub-project component.
- Prototyping the deppy OLM 1.x sub-project component.
- Phase 0 has been marked as dev complete.
- Defining a WIP roadmap for phase 1+.

## Additional Context

TODO: Organize this better.

- See the [OLM 1.x wiki](https://docs.google.com/document/d/1-7_bnsSwM4vtpDo1jcdBNyLbMPi-Q39wpr2dx2IsO-I/edit#) for more information on the rukpak, deppy, etc sub-projects.
- The pre-requisite to platform operators was building out the rukpak OLM sub-component.
- The current PlatformOperators API is a lightweight wrapper around the top-level Operator API that has yet to be built out. Early phases will continue to build out the OLM 1.x control plane, while later phases may elect to manage an Operator API under-the-hood and/or support configuring platform operators before a control plane is available.

## Resources

TODO: Organize this better into buckets.

### Current

- [RFE](https://issues.redhat.com/browse/RFE-664)
- [Platform Operators Feature](https://issues.redhat.com/browse/OCPPLAN-9555)
- [Optional Capabilities Feature](https://issues.redhat.com/browse/OCPPLAN-7589)
- [Market Problem](https://issues.redhat.com/browse/OCPPLAN-9638)
- [Composable OpenShift RoadMap](https://docs.google.com/document/d/1srswUYYHIbKT5PAC5ZuVos9T2rBnf7k0F1WV2zKUTrA/edit#heading=h.mduog8qznwz)
- [Composable OpenShift Presentation](https://docs.google.com/presentation/d/1U2zYAyrNGBooGBuyQME8Xn905RvOPbVv3XFw3stddZw/edit#slide=id.g10555cc0639_0_7)
- [4.11 Technical Enablement Slides](https://docs.google.com/presentation/d/150M-iMxbUqSmzaGu6rwD7uEtFi24BCHl30tO8I2pUbM/edit)
- [4.12 Technical Enablement Slides](https://docs.google.com/presentation/d/1ROv_YG222qXD485QO4b-aHeIYW0Gxd1KVT3SYu_SLvM/edit#slide=id.g148a5346ab5_0_0)
- [Phase 0 Enhancement Proposal](https://github.com/openshift/enhancements/blob/master/enhancements/olm/platform-operators.md)
- [Initial dev phase 0 documentation](https://gist.github.com/timflannagan/5490dc7471831da11772cd695512b863)
- [Initial Install Flexibiltiy Conversations](https://drive.google.com/file/d/1Br2IgCbZTHQej2IswK-NgCDFFM_HexdD/view)
- [Install Flexibility Feature](https://issues.redhat.com/browse/OCPPLAN-8156)
- [Initial registry+v1 provisioner notes](https://docs.google.com/document/d/1JiS0WiWc3DlvyF719dK0hoxkDx4WQ3lg5Bjfhu2wpng/edit)

### Prior ART

- [FeatureSet Strawman](https://www.google.com/url?sa=t&rct=j&esrc=s&source=appssearch&uact=8&cd=0&cad=rja&q&sig2=j0S1vWmFCAU41-yDImn8jA&ved=0ahUKEwiljrHW96b6AhXQS6sCHR45C184ABABKAAwAA&url=https://drive.google.com/a/redhat.com/open?id%3D1jT8s3RVFU-ZCy1_9aaAln3e274TDjvAusLM7Fv3Prko%26usp%3Dchrome_omnibox&usg=AOvVaw0ke3fzB1T1jBVqNvhKAfKM)
- [Pre-phase 0 enhancement](https://www.google.com/url?sa=t&rct=j&esrc=s&source=appssearch&uact=8&cd=0&cad=rja&q&sig2=gZTBtrji7JadecBn-RMJoQ&ved=0ahUKEwifmfTl96b6AhXMSasCHb86DpU4ABABKAAwAA&url=https://drive.google.com/a/redhat.com/open?id%3D1qwbrvokZq9LSRm_4NKNAHKa6i0Wsaw6I8-E09v13xH8%26usp%3Dchrome_omnibox&usg=AOvVaw3VYo4bT6Ytf4nOpy2nKvzZ)
- [Day 0 braindump from ben/shawn/justin](https://docs.google.com/document/d/1xgrQp_TdmJtGYZn8Bvm_GCslHYsFhvb8SdMVnV8dWc0/edit#heading=h.oxn6wh783wc4)
- [Day 0 operator characteristics spreadsheet](https://docs.google.com/spreadsheets/d/12g5P8w4SyUMUXEfgvwT7C75PRHHI3-U8JsiRom1LqqU/edit#gid=0)

## Open Questions

TODO: Consolidate with the EP and other hackmds in my personal drive.

- What operators would require preflight checks before upgrading platform operators?
- Does the cluster participation model need to encorporate pre-apiserver upgrades and post-apiserver upgrades?
- Do platform operators require dependency resolution? Do we support platform operators depending on other platform operators? What about GVK dependencies?
- What does a console integration look like for platform operators?
- Does implementing platform operators before the control plane has started influence how platform operators integrate with hypershift in the future?