Skip to content

Keep a n-1 version of Nginx Ingress Operator in Bundle #618

@haywoodsh

Description

@haywoodsh

Update the creation of the Operator Bundle to make the previous NIC operator version available.

Discussed in #540

Originally posted by fperearodriguez August 7, 2025
Hi team,

I would like to suggest keeping old versions of the operator available for installation in the certified-operators index.

Thinking about this issue Failed install, an old version was not available to install, so we couldn't do a downgrade to a known good one.

I guess that promotion strategy is intentional, and considering scenarios in which using an old version could be helpful, I would appreciate it if you reconsider changing this strategy.

As you can see in the following code block, only the latest version is available in the registry.redhat.io/redhat/certified-operator-index:v4.19 index, channel alpha:

catalog-browser --image registry.redhat.io/redhat/certified-operator-index:v4.19 show package nginx-ingress-operator
Package: nginx-ingress-operator
Channels:
 - nginx-ingress-operator/alpha
Bundles:
 - nginx-ingress-operator.v3.2.2

Thanks,
Fran

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready for refinementAn issue that was triaged and it is ready to be refined

    Type

    No type

    Projects

    Status

    Todo ☑

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions