Multiple active upgrade path for operator

[Nilesh20]

I have operator and currently wanted to have multiple active versions of it.

ex: Previously

bundle versions were 100 -> 110> 200 -> 300 (Here new version replaces the old one when published)
Now I want update on 110 i.e 110->120-> 130 and meanwhile expecting update on 300 like 300 -> 400

How I can achieve such upgrade path ?

I was trying to use multiple channels, will that be correct.

Type of question

Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?

Question

What did you do?
A clear and concise description of the steps you took (or insert a code snippet).

What did you expect to see?
A clear and concise description of what you expected to happen (or insert a code snippet).

What did you see instead? Under which circumstances?
A clear and concise description of what you expected to happen (or insert a code snippet).

Environment

• operator-lifecycle-manager version:

• Kubernetes version information:

• Kubernetes cluster kind:

Additional context
Add any other context about the question here.

[narasimha-ntnx]

Hi @Nilesh20 I am also facing a similar issue. Can you please explain me how to achieve this ?

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

[nilesh-salunkhe-sp]

@narasimha-ntnx It's too old issue now, I don't remember completely but I thik I achieved it earlier using multiple channels.