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

Fix CaaSP version in Helm 2 to 3 Migration section #977

Merged
merged 1 commit into from
Aug 20, 2020
Merged
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
Fix CaaSP version in Helm 2 to 3 Migration section
  • Loading branch information
pgonin committed Aug 20, 2020
commit 5cc14f23d5e39692be7b516683a0ba046c5883fa
4 changes: 2 additions & 2 deletions adoc/admin-software-installation.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -222,15 +222,15 @@ The process for migrating an installation from Helm 2 to Helm 3 has been documen

==== Preconditions

* A healthy CaaSP 5.0 installation with applications deployed using Helm 2 and Tiller.
* A healthy CaaSP 4.5 installation with applications deployed using Helm 2 and Tiller.
* A system, which `skuba` and `helm` version 2 have run on previously.
** The procedure below requires an available internet connection to install the `2to3` plugin. If the installation is in an air gapped environment, the system may need to be moved back out of the air gapped environment.
* These instructions are written for a single cluster managed from a single Helm 2 installation. If more than one cluster is being managed by this installation of Helm 2, please reference https://github.com/helm/helm-2to3 for further details and do not do the clean-up step until all clusters are migrated.


==== Migration Procedure

This is a procedure for migrating a CaaSP 5.0 deployment that has used Helm 2 to deploy applications.
This is a procedure for migrating a CaaSP 4.5 deployment that has used Helm 2 to deploy applications.

. Install `helm3` package in the same location you normally run `skuba` commands (alongside the helm2 package):
+
Expand Down