Making a Kubernetes cluster change through GitHub

Your local Kubernetes cluster, through Flux, will update to reflect changes in the Git repo. Any change in Git will be propagated to the cluster after a few minutes.

Let's see this with a test updating the number of pods in the frontend deployment:

1. Change the Chapter08/example/frontend/deployment.yaml file in your forked repo as described here:

---
apiVersion: apps/v1
kind: Deployment
metadata:
    name: frontend
    labels:
        app: frontend
    namespace: example
spec:
    replicas: 2

This changes the number of replicas from 4 to 2.

2. Commit the change into the master branch and push into the GitHub repo.
3. Monitor the cluster with the following command:

$ kubectl get pods -n example -w

You will see how the number of frontend pods will decrease after a few minutes. You can speed it up by manually syncing Flux.

4. Revert the change...