Not few of us are struggling with the fact that sometimes one needs an operator in a given version despite all other versions in the catalog/channel.
There are very low options there and all of them rely on automation and manual approval of install plan for such installations (that are expected to have a Manual + startingCSV pair). And everyone's reinventing the wheel using ansible, acm, k8s jobs, disconnected mirrors with only one version, etc. again and again.
I'm not sure if this has been discussed before, but it would be really great if OLM can be smart enough to cover this use case: whenever a subscription is created, if the startingCSV field is defined and the installPlanApproval is properly set to this new value, install that version automatically but let the subscription remain in Manual. It can be a one shot comparison at creation time, no need to add extra logic for recurring modifications.
soukron
commented
3 months ago
Not few of us are struggling with the fact that sometimes one needs an operator in a given version despite all other versions in the catalog/channel.
There are very low options there and all of them rely on automation and manual approval of install plan for such installations (that are expected to have a Manual + startingCSV pair). And everyone's reinventing the wheel using ansible, acm, k8s jobs, disconnected mirrors with only one version, etc. again and again.
I'm not sure if this has been discussed before, but it would be really great if OLM can be smart enough to cover this use case: whenever a subscription is created, if the startingCSV field is defined and the installPlanApproval is properly set to this new value, install that version automatically but let the subscription remain in Manual. It can be a one shot comparison at creation time, no need to add extra logic for recurring modifications.