Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README minor updates #2

Open
wants to merge 1 commit into
base: readme/development-in-the-cluster
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -270,6 +276,13 @@ oc logs -f console-operator-<sha> -n openshift-console-operator
oc exec -it console-operator-<sha> -- /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:
Expand Down