Epic Goal

• To make the release process for OLM V1 simple and repeatable by creating tools, repositories, and documented processes.
• To make the installation process for OLM V1 simple and repeatable.

Background

The goal of this milestone is to make it easy to create and distribute an official OLM V1 Release. As you may know, the OLM V1 experience is primarily powered by a few subprojects, the Operator Controller, RukPak, Cert Manager, and potentially the new CatalogSource project once it is created. It is unreasonable to ask users to install each of these components independently, so creating an official process for releasing, distributing, and installing the project is valuable not only to our developers but our customers as well:

Why is this important?

• Making it easy for developers to cut an OLM V1 Release will promote frequent releases.
• Making it easy for users to install and test OLM V1 Releases will promote adoption and community feedback.

Scenarios

1. As a developer, I would like to cut a new release of OLM V1 by following a documented process.
2. As an OLM user, I would like to install a new release of OLM V1 by following a documented process.

Upstream Ticket

https://github.com/operator-framework/enhancements/issues/123

Acceptance Criteria

• CI - MUST be running successfully with tests automated.
• Release process is documented.
• An OLM V1 Milestone 1 release is cut.

Done Checklist

• CI - CI is running, tests are automated and merged.