Usage Information

Dependencies

• Kubernetes Cluster: v1.20
• kubectl 
• Helm 
• Flux  installed on your cluster: v0.39.0
• cert-manager  installed on your cluster: v1.5.0

Install Flux onto the cluster if not already installed

flux install

Helm Install Weave GitOps Assured Chart

helm install --namespace weave-gitops-assured weave-gitops-assured oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/weaveworks/weave-gitops-assured --version 0.1.2

Create a password for the admin user

Weave GitOps uses a bcrypt hash for passwords. Therefore, you must keep this in mind when creating and/or updating Weave GitOps login passwords.

To change the password, simply create a .yaml file as below and apply using helm upgrade:

File: weave-gitops-password.yaml

NOTE: the Weave GitOps UI will not be accessible until the password YAML is applied.

Access the Weave GitOps UI

Use the username and password created above to access the UI via:

kubectl -n weave-gitops-assured port-forward svc/weave-gitops-assured 9001:9001

You can access the Weave GitOps UI at https://localhost:9001 

Observing the health of your installation via CLI and kubectl

You can check the health of your installation by running:

kubectl get deploy -n flux-system

Check that all deployments are ready. If not, you can check the logs of the failing deployments to see what went wrong. Example:

kubectl logs -n flux-system deploy/helm-controller

EKS via AWS Console

You can also check the health of your installation via the AWS Console. Go to the EKS service and select your cluster. Then go to the Resources tab and select Deployments. You should see all the deployments in the flux-system namespace. Check that all deployments are ready. If there are any issues, you can check the status of the deployment by clicking on it. This will often give you a clue as to what went wrong.