-
Notifications
You must be signed in to change notification settings - Fork 90
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
Add manifests to the published releases #292
Comments
Thanks @dierbei. The goal here is to release also bare manifests of the Kamaji operator, in order to allow consumers to install Kamaji without using Helm, by applying the manifests bundle. Moreover, the manifests bundle could be either split between CRD and controllers or it could contain both (all-in-one). |
@maxgio92 Thanks for your answer. If I understand correctly, it is necessary to add crd, controller and other related yaml files when releasing, right? Pack them in a separate tarball file. In this way, you can use kubectl to install directly. |
Agree @prometherion. |
Feature
Release both binaries and operator manifests (CRDs, webhook configurations, controller, RBAC, etc.).
Motivation
Consumers might need or want to install Kamaji from bare manifests, without the requirement of using Helm.
Additional context
A practical scenario can be kamajictl which can install a specific version of Kamaji, by downloading and applying its released manifests.
Goreleaser could then be leveraged to bundle in the release archive binaries, manifests, signatures, etc. (e.g. https://github.com/fluxcd/kustomize-controller/blob/main/.goreleaser.yaml#L6).
The text was updated successfully, but these errors were encountered: