#1743: Begin generating the operator bundle using operator-sdk #1811
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* operator-sdk requires storage version to be specified for each crd
* Makefile * OPERATOR_VERSION removes -SNAPSHOT suffix as invalid domain for version field while executing `operator-sdk generate...` * Adds recipes for constructing both the manifests and bundle, adapted from the demonstration versions * Uses recursive rule-making to avoid duplication and work around the limits of controller-gen & operator-sdk * script/add_licence.sh * Script for prepending the licence header to generated files * script/gen_crd.sh * adds config directory for crd generation * PROJECT * Scaffolding configuration for operator-sdk executable * config * root configuration directory for kustomize and operator-sdk * samples directory locates the alm-examples used in the bundle manifest * rbac directory locates the permissions, cluster-permissions and deployments fields in the bundle manifest * prometheus directory used for monitoring resources although doesn't seem to be applicable at the moment (prometheus-jmx-exporter.yaml is invalid) * crd directory locates the CRDs generated in the same manner as that in the deploy directory * All resources have to be copied in - cannot use symlinks and both controller-gen and operator-sdk will error * Limitations of process: * controller-gen cannot generate CRDs across modules (directory containing go.mod) so gen-crds.sh changes directory into pkg/apis in order to execute successfully * operator-sdk has to execute in root of directory and cannot generate across modules. Also, seems to have a duplication problem if 2 apis are being processed with one dependent on the other. So copy apis 1 at a time & process * Result is `make bundle` will regenerate csv manifests (if required) then create a bundle directory containing these manifests and other artifacts necessary for deploying an image for the Operator Hub and OLM catalogue
astefanutti
approved these changes
Nov 19, 2020
|
Let's merge this and iterate on it in subsequent PRs. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Provides build hooks for OLM bundle generation. Uses the latest functionality available from the operator-sdk 1.0.0.
Release Note