[WIP] bundle: add subcommand to build operator index images#2714
[WIP] bundle: add subcommand to build operator index images#2714estroz wants to merge 1 commit intooperator-framework:masterfrom
add subcommand to build operator index images#2714Conversation
fa1c740 to
fabd753
Compare
| // buildOPM reates and download 'opm' to a binary directory using 'go get' to | ||
| // download a particular version, specified by registryVersion, to install. | ||
| // TODO(estroz): shell out to make after kubebuilder integration. | ||
| func (c bundleIndexCmd) buildOPM(binaryPath string) error { |
There was a problem hiding this comment.
@ecordell is in the process of creating a downstream build of opm. Does it make more sense for the registry project to just include a release of the opm binary that could be downloaded -- or perhaps even just a container image to extract it from like opm itself does to do the container image build -- rather than compiling from source?
Trying to avoid requiring golang as a dependency if possible.
|
@kevinrizza the intent wasn't to supersede your PR, but now that its closed I'll split your commit along with some changes unrelated to |
a2468da to
18f41b5
Compare
doc,website: regenerate cli docs CHANGELOG.md: 'bundle add' addition
18f41b5 to
9eef07b
Compare
|
/hold There's some recent debate (as of today) about how the UX for this should work in SDK. We don't necessarily want to have commands in SDK that duplicate The thought is that we want to enable running the operator via OLM by deploying it via an index image containing the operator bundle AND the operator dependencies. But we might want to hide the details of the catalog under a simpler SDK workflow. |
|
@estroz: PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Closing until we have a better idea of how we want to structure a bundle index feature. |
Description of the change:
operator-sdk bundle addshells out toopmto build index images that encapsulate multiple operator versions.Motivation for the change: users should be able to ship multiple versions of their operator in the index image format after building an operator image with
bundle create.Note: operator-registry sports a Go library to handle index building, but it requires
operator-sdkbe built withCGO_ENABLED=1. This is currently not possible due to k8s dependency requirements, hence the shell-out toopm.TODO:
bundlecommand doc updateindex addrequires image be present remotely operator-registry#226 addressed before merge/kind feature