How to: Upgrade to Weave Gitops Enterprise
Upgrading requires we:
- Already have Weave GitOps installed on the cluster
- Install Profiles onto the cluster
- Apply the entitlements secret
- Check that Weave Gitops Enterprise has been installed
2. Install profiles
This step will be removed
This step will be removed when Profiles are included in Weave Gitops
Download the latest
pctl release and install the Profile custom resources:
pctl install --flux-namespace wego-system
3. Apply the entitlements secret
Contact firstname.lastname@example.org for a valid entitlements secret. Then apply it to the cluster:
kubectl apply -f entitlements.yaml
Run the upgrade command from a local copy of git repo that is sync'd to the cluster:
A Pull Request will be created against your cluster repository. Review and merge this pull request to upgrade to Weave Gitops Enterprise.
5. Configure Weave Gitops Enterprise
Weave Gitops Enterprise has a number of configration options but two importants aspect to configure are:
An Ingress 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.
- kind clusters
- Other cloud providers
To determine the public IP address of the worker nodes of your cluster get the local IP for kind:
export INGRESS_ADDRESS=$(ipconfig getifaddr en0)
For other cluster providers you'll have to configure the ingress around what they provide.
agentTemplate.natsURL value in the Weave Gitops Enterprise
ConfigMap in your config repo.
5.2. Git repository configuration
WGE will make pull requests against your git config repo when creating new CAPI clusters etc. The
GIT_PROVIDER_TOKEN in the
git-provider-credentials secret specified above will be used to authenticate.
capi.config.repositoryURL with the correct url to your git config repository in the Weave Gitops Enterprise
ConfigMap in git config repository itself.
After configuring values in the
ConfigMap you may have to delete the cluster-service pod for the changes to take effect.
6. Checking that WGE is installed
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