You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Allow to depend on CVO operators, not only on OLM-managed operators. In other words, I'd like to express that my operator depends, say, on NTO >= x.y.z and other OLM managed operands.
Up until now, we are using minKubeVersion as minimum proxy for that requirement: knowing that NTO version is bound to the OCP version and that each OCP version is based on a well known kubernets version, we use minKubeVersion to encode this requirement, but we would like to have it more explicit.
Feature Request
Is your feature request related to a problem? Please describe.
Allow to depend on CVO operators, not only on OLM-managed operators. In other words, I'd like to express that my operator depends, say, on NTO >= x.y.z and other OLM managed operands.
Up until now, we are using
minKubeVersion
as minimum proxy for that requirement: knowing that NTO version is bound to the OCP version and that each OCP version is based on a well known kubernets version, we useminKubeVersion
to encode this requirement, but we would like to have it more explicit.Describe the solution you'd like
Extend https://github.com/operator-framework/enhancements/blob/master/enhancements/operator-dependency-resolution.md#syntax in such a way we can depend on CVO operators. Random example only for illustration purposes
The text was updated successfully, but these errors were encountered: