Add installing an operator instance from existing O/OV in the cluster
#1678
Assignees
Labels
Comments
zen-dog
pushed a commit
that referenced
this issue
Sep 18, 2020
…1680) Summary: The current `kudo install ...` command accepts either a remote repo operator name, a URL or a local folder/tgz. This PR allows the user to install an instance of an existing in-cluster operator version using the newly introduced `--in-cluster` option: ``` ❯ ./bin/kubectl-kudo install first-operator --operator-version=0.2.0 --in-cluster operatorversion default/first-operator-0.2.0 already installed instance default/first-operator-instance created ``` This way `kudoctl` will only look for already installed operator versions (one can list them using `kudoctl get operatorversions`) and does not need access to the repo/package files. Fixes #1678 Signed-off-by: Aleksey Dukhovniy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: