What would you like to be added:
The Current kudo install ... command accepts either a remote repo operator name, a URL or a local folder/tgz. However, in a situation where an operator was already installed in the cluster (the corresponding Operator/OperatorVersion resources exist), it should be possible to simply install an Instance of the said operator from the kudoctl.
Why is this needed:
Imagine a scenario where there is already an operator installed (by e.g. cluster admins) but the user wants to have her own Instance of that operator due to security, performance, or other concerns. The user may not have access to the original operator package nor does he need to, as O/OV are already in the cluster and all that is missing is the Instance resource.
What would you like to be added: The Current
kudo install ...command accepts either a remote repo operator name, a URL or a local folder/tgz. However, in a situation where an operator was already installed in the cluster (the correspondingOperator/OperatorVersionresources exist), it should be possible to simply install anInstanceof the said operator from the kudoctl.Why is this needed: Imagine a scenario where there is already an operator installed (by e.g. cluster admins) but the user wants to have her own Instance of that operator due to security, performance, or other concerns. The user may not have access to the original operator package nor does he need to, as
O/OVare already in the cluster and all that is missing is theInstanceresource.