Gloo Edge API Gateway Multi-cluster Provisioning with GitOps
Since it’s a popular customer question, today we want to show you how to automate provisioning of a Gloo Edge API Gateway on Kubernetes, so we turned to GitOps. If you want to jump straight to it, the Solo.io blog Github repo contains step by step information to setup your first Gloo Edge provisioning via Fluxcd.
API Gateway Multi-cluster Provisioning for Non-production
The intended use case for these instructions is primarily for testing and learning. While there is always a focus on managing production environments, we believe that non-production environments are equally, if not more, important. This is particularly true for software development organizations, where code progresses from the developer laptop via non-production environments to production. Yet it’s not just software development teams that use multiple environments. If there is one thing we have learnt from 30+ years of building IT systems, it is that we always need to test our changes (for example, OS patches) before going to production.
We’re not going to talk about API Gateways or GitOps here. If you’re reading this blog, you likely understand and have defined both these topics in your own way. At Solo.io, we have talked about GitOps and our products a few times over the years; there are a few links at the end of the blog.
The ideal test environment is the one that is a temporary clone of production. That way we know 100% that the change we want to make will work when promoted to production. Also we don’t have to bear the cost of maintaining numerous non-production environments. Tear down and rebuild as need be. So how do we work towards this approach?
Our set-up for API Gateway Provisioning with GitOps
In this blog, we’ll use Fluxcd (GitOps) to clone Kubernetes (K8s) clusters. Git commits will be used to configure the API Gateway with:
- Rate limiting
To dive into the example, the Solo.io blog Github repo contains the step-by-step information to setup your first Gloo Edge provisioning via Fluxcd. The Blog Git repo has a preamble section, but if you’re already familiar with Fluxcd, you could skip to the “End of Preamble” section.
Learn more about API Gateway Provisioning with GitOps
Hopefully these instructions linked above will allow you to take a closer look at how to automate your Gloo Edge provisioning via GitOps on Kubernetes. There is no silver bullet here, but a GitOps methodology (whichever tool you chose) will solve business challenges and should be part of your adoption roadmap. Solo.io products and people are ready for this journey with you.
Please also see some of our other blogs around this topic: