How should I have 2 bundles config with SDK?

[camilamacedo86]

Type of question

Best practices

Question

How should I have 2 bundles versions with SDK?

What did you do?

• I want to have a bundle for upstream and another for downstream for example which have diff CSV specs

OR

• I want to have a bundle that will serve k8s versions which are lower than 1.15 and another one that is upper to that.

What did you expect to see?

That SDK CLI allows me to do that and doc which helps to know how can I customize my project to do that since that shows to be a common scenario.

What did you see instead? Under which circumstances?

No option/guidance available.

Environment

Operator type:

/language go /language ansible /language helm

[camilamacedo86]

Just to register. As discussed in the bug triage meeting it is currently not supported. However, it was accepted as an RFE and is required to check how that could be addressed.

[estroz]

FWIW running the following seems to create two bundles, assuming you have two different operator configurations in config/manifests-{foo,bar}:

export PACKAGE_NAME=$(cat PROJECT | grep projectName | sed 's/projectName: //')
for sub in "foo" "bar"; do
	mkdir -p bundle-$sub
	pushd bundle-$sub
	kustomize build ../config/manifests-$sub | operator-sdk generate bundle --version 1.2.3 --kustomize-dir ../config/manifests-$sub --package $PACKAGE_NAME
	popd
done

I alluded to ^ in https://github.com/operator-framework/operator-sdk/issues/4586#issuecomment-78833789.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[estroz]

/lifecycle frozen