Skip to content

Doc update for run bundle-upgrade #4968

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 7, 2021
Merged

Doc update for run bundle-upgrade #4968

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 6 additions & 3 deletions website/content/en/docs/olm-integration/testing-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,9 +118,12 @@ Let's look at the anatomy of the `run packagemanifests` configuration model:

`operator-sdk run bundle-upgrade` assumes OLM is already installed and running on your
cluster and that the Operator has a valid [bundle][bundle-format]. It also assumes that
the previous version of the Operator was deployed on the cluster using `run bundle` command
or traditionally via OLM. See the [CLI overview][doc-cli-overview] for commands to work
with an OLM installation and generate a bundle.
the previous version of the Operator was either deployed on the cluster using `run bundle`
command or traditionally via OLM. Another assumption of this command is that the newer operator bundle
should not exist in the index image, if the previous version of the operator bundle was installed
traditionally using OLM. This will cause the registry pod to fail as the bundle is already added to the
index that provides package and csv. See the [CLI overview][doc-cli-overview] for commands to work with
an OLM installation and generate a bundle.

```
operator-sdk run bundle-upgrade <bundle-image> [--kubeconfig=] [--namespace=] [--timeout=]
Expand Down