From 6e08b9db57d2a773246ad23ff8519860833ca102 Mon Sep 17 00:00:00 2001 From: rashmigottipati Date: Sun, 6 Jun 2021 22:54:59 -0400 Subject: [PATCH] Update assumptions on `run bundle-upgrade` to include a scenario Signed-off-by: rashmigottipati --- .../en/docs/olm-integration/testing-deployment.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/website/content/en/docs/olm-integration/testing-deployment.md b/website/content/en/docs/olm-integration/testing-deployment.md index 8862c21a767..3248dcb4f7c 100644 --- a/website/content/en/docs/olm-integration/testing-deployment.md +++ b/website/content/en/docs/olm-integration/testing-deployment.md @@ -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 [--kubeconfig=] [--namespace=] [--timeout=]