operator-framework / operator-framework/operator-sdk

How should I have 2 bundles config with SDK?

Open
#4,754 4 comments 0 reactions 1 assignee View on GitHub

@estroz is already working on this.

Since Apr 19, 2021.

language/ansible language/go language/helm lifecycle/frozen olm-integration
Dominant language
Go
Stars
7.7k
Forks
1.8k
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.