Remove deprecated templates; Move installplan to operatorhub (#83)

redhat-cop · Jun 3, 2021 · d7dd9d3 · d7dd9d3
1 parent 7979fd7
commit d7dd9d3
Show file tree

Hide file tree

Showing 5 changed files with 3 additions and 26 deletions.
diff --git a/operatorhub/README.md b/operatorhub/README.md
@@ -5,7 +5,9 @@ The below templates are used to deploy Operators from OperatorHub without having
 To do this you would create the following in order:
 
 1. [OperatorGroup](operatorgroup.yml)
-1. [CatalogSourceConfig](catalogsourceconfig.yml)
 1. [Subscription](subscription.yml)
 
 For more details, you can see the documention [here](https://docs.openshift.com/container-platform/4.1/applications/operators/olm-adding-operators-to-cluster.html#olm-installing-operator-from-operatorhub-using-cli_olm-adding-operators-to-a-cluster).
+
+
+There are also situations where you only want to work with a specific version of an operator. To avoid dealing with automatic updates, you can set your `installPlan` in your subscription to `Manual` and then utilize the installplan-approver templates located in this repository to deploy a job that will automatically approve that version of the operator (but will not proceed with any future automatic updates)
diff --git a/operatorhub/catalogsourceconfig.yml b/operatorhub/catalogsourceconfig.yml
diff --git a/...ver/installplan-approver-job-template.yml → ...hub/installplan-approver-job-template.yml b/...ver/installplan-approver-job-template.yml → ...hub/installplan-approver-job-template.yml
diff --git a/...llplan-approver-role-binding-template.yml → ...llplan-approver-role-binding-template.yml b/...llplan-approver-role-binding-template.yml → ...llplan-approver-role-binding-template.yml
diff --git a/...er/installplan-approver-role-template.yml → ...ub/installplan-approver-role-template.yml b/...er/installplan-approver-role-template.yml → ...ub/installplan-approver-role-template.yml