Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create installation yaml for operator-controller #109

Closed
Tracked by #123
dtfranz opened this issue Feb 1, 2023 · 2 comments
Closed
Tracked by #123

Create installation yaml for operator-controller #109

dtfranz opened this issue Feb 1, 2023 · 2 comments
Assignees

Comments

@dtfranz
Copy link
Contributor

dtfranz commented Feb 1, 2023

Each component of OLM v1 should be installed through a consistent format. RukPak, for instance, is currently installed using a single downloadable yaml file (here). We should create a similar if not identical installation method for the operator-controller. If we choose to go another route, an additional issue must be created to do the same for RukPak (and probably cert-manager too).

Acceptance criteria:

  • operator-controller can be installed from a single downloadable yaml file.

Note that the output of this issue should not install dependencies such as RukPak itself, just as RukPak does not install its dependencies through the same yaml. This should be taken care of in the next issue: #110 Also note that installing the operator-controller on its own through this yaml without installing the dependencies will not result in a successful installation. This information should be easily available so that users don't install this yaml only hoping for a successful OLM V1 installation. We should also have links to documentation for #110 available.

Possible idea: Install operator-controller via BundleDeployment

@dtfranz
Copy link
Contributor Author

dtfranz commented Feb 23, 2023

Addressing in #133

@dtfranz
Copy link
Contributor Author

dtfranz commented Mar 7, 2023

Closed with #133

@dtfranz dtfranz closed this as completed Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants