policy(ironbank): default to 10.x

[v1v]

Breaking change, no more support for 9.x but 10.x by default.

consumers can override ubi_version_path: https://repo1.dso.mil/dsop/redhat/ubi/9.x/ubi9

[fr4nc1sc0-r4m0n]

LGTM

[fr4nc1sc0-r4m0n]

LGTM

[v1v]

I'm unsure how to proceed here as this is a breaking change and the updatecli policies will try to update to 1.0.0 - I bet we will need to do the changes manually in all the consumers to move to ubi10, once we agree

[fr4nc1sc0-r4m0n]

I'm unsure how to proceed here as this is a breaking change and the updatecli policies will try to update to 1.0.0 - I bet we will need to do the changes manually in all the consumers to move to ubi10, once we agree

Can we create a new major version and let updatecli do the changes automatically by us? Am I missing something?

[v1v]

Can we create a new major version and let updatecli do the changes automatically by us? Am I missing something?

This is more about PRs being created automatically and repository owners merging them. I don't know whether they understand the implications of moving from 9.x to 10.x, or whether they need to run some e2e tests to validate that things work as expected. However, there is no concept of e2e at the moment; those ubi container images cannot be used locally.

We can potentially release 1.0.0 and let the different repository owners who have PRs for 10.x submit them; they can handle any validations on their end. Probably this is more about awareness thatn anything else