Skip to main content
Version: 0.3.0

Upgrading

How to: Upgrade to Weave Gitops Enterprise#

Upgrading requires we:

  1. Already have Weave GitOps installed on the cluster
  2. Choose a database
  3. Create a secret for docker repository
  4. Create a secret for creating pull requests on your git provider
  5. Determine the public IP address of the worker nodes
  6. Install the helm chart
  7. Check that Weave Gitops Enterprise has been installed (optional)

2. Choosing a database#

WGE stores incoming data from the connected clusters to a relational database. It supports SQLite and PostgreSQL.

3. Creating a secret for docker repository#

Create a secret that contains your docker repository credentials. This secret will be used by Kubernetes during deployment in order to pull down the WGE images. You can find instructions on how to generate this secret here.

$ kubectl create secret docker-registry \  --namespace wego-system docker-io-pull-secret \  --docker-username=<your-docker-username> \  --docker-password=<your-docker-password>

If you use a secrets management solution such as Sealed Secrets follow their instructions on how to create a new secret.

Take note of the secret name as you will need to supply it later when installing the chart.

4. Create a secret for creating pull requests on your git provider#

A Personal Access Token is required for the WGE to create pull requests for new clusters. These tokens need certain permissions (scopes) set. For

  • GitHub: repo
  • GitLab: api

Save the token in secret called git-provider-credentials.

kubectl create secret generic git-provider-credentials \  --namespace=wego-system  --from-literal="GIT_PROVIDER_TOKEN=$GITHUB_TOKEN"

5. Determining the public IP address of the worker nodes#

You need to determine the public IP address of the worker nodes of your cluster. This IP address is necessary in order to establish connectivity between agents and your WGE instance. The way to determine this depends on your cluster type and provisioning method. Take note of that IP address as you will need to supply it later when installing the chart.

6. Installing the Helm chart#

Before installing the chart, you need to add the Helm chart repository and then update its local cache. Run the following commands:

$ helm repo add wkpv3 https://s3.us-east-1.amazonaws.com/weaveworks-wkp/charts-v3  "wkpv3" has been added to your repositories$ helm repo update  Hang tight while we grab the latest from your chart repositories...  ...Successfully got an update from the "wkpv3" chart repository  Update Complete. ⎈Happy Helming!

Finally install the Helm chart to the target namespace by executing the following command using the Helm CLI (>= v3.5.4).

7. Checking that WGE is installed (optional)#

You should now be able to load the WGE UI by running the following command:

$ kubectl port-forward --namespace wego-system deployments.apps/mccp-nginx-ingress-controller 8000:80

The WGE UI should now be accessible at http://localhost:8000.

How to: Install the MCCP CLI#

The MCCP CLI allows you to interact with Weave GitOps Enterprise management clusters. You can use mccp to manage the lifecycle of your infrastructure declaratively using GitOps. The latest version of the MCCP CLI is available in the following links: