FluxCD GitOps debugging tip

After enabling E2E testing of FluxCD powered GitOps continuous deployment, the feedback of new commits are quite slow. Because you have to wait for the E2E testing result, lots of time cost on setuping the environment and provisioning your development from scrath.

Inspired by E2E testing in Github actions, the DevOps engineers can build local debugging environment in Kind or minikube.

Below is a script how using Kind to provision FluxCD then reconciling the latest commits by FluxCD.

Posts in this Series

    comments powered by Disqus