From 8e3463874b04f6d65b2c5cfea34a12c80bcdb7b9 Mon Sep 17 00:00:00 2001 From: Jakub Hadvig Date: Wed, 13 Feb 2019 14:08:49 +0100 Subject: [PATCH] README minor updates --- README.md | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b8f594d06..8af6db0af 100644 --- a/README.md +++ b/README.md @@ -158,9 +158,9 @@ We don't want the default `console-operator` to run if we are going to test our the following: ```bash -# Instruct CVO to stop managing the console operator -# CVO's job is to ensure all of the operators are functioning correctly -# if we want to make changes to the operator, we need to tell CVO to stop caring. +# Instruct CVO to stop managing the console operator. +# CVO's job is to ensure all of the operators are functioning correctly. +# If we want to make changes to the operator, we need to tell CVO to stop caring. oc apply -f examples/cvo-unmanage-operator.yaml # Then, scale down the default console-operator oc scale --replicas 0 deployment console-operator --namespace openshift-console-operator @@ -226,6 +226,12 @@ And ensure that the `imagePullPolicy` is still `Always`. This will ensure a fas imagePullPolicy: Always ``` +Apply the updated operator manifest: + +```bash +oc apply -f ~/05-operator-alt-image.yaml +``` + #### Deploying At this point, your pattern will be @@ -270,6 +276,13 @@ oc logs -f console-operator- -n openshift-console-operator oc exec -it console-operator- -- /bin/bash ``` +#### Restore default settings +In order to restore the default `console-operator`, we need to start CVO to manage the operators. + +```bash +oc apply -f examples/cvo-manage-operator.yaml +``` + ## Tips If you don't know where your `kubeconfig` is due to running against multiple clusters this can be handy: