Navigating the Integration of Logic Apps with Kubernetes and Azure Arc

Businesses are constantly seeking innovative solutions to optimise their operations, enhance scalability, and ensure regulatory compliance. One of the emerging trends in this domain is the integration of Logic Apps with Kubernetes, facilitated by Microsoft’s Azure Arc technology. This approach offers a promising avenue for organisations to leverage the robustness of Kubernetes clusters while benefiting from the agility and efficiency of Logic Apps. In this discussion, we delve into the nuances of running Logic Apps under Kubernetes, explore the potential benefits and challenges, and examine the strategic considerations for organisations contemplating this integration. Whether you’re looking to extend your existing Kubernetes investments or seeking a cost-effective solution for managing small to large workloads, understanding the interplay between these technologies is crucial for making informed decisions that align with your business objectives.

One question we get asked a lot is about running Logic Apps under Kubernetes. This is something that’s currently a feature in preview because Azure Arc—start again, discuss it, keep it running. We’ll just cut it. Okay, one question we get asked a lot is about running Logic Apps under Kubernetes, which is currently in preview. Microsoft has a technology called Azure Arc which allows you to register Kubernetes clusters and manage them in one place, whether they are in Azure, in another cloud, or even on-premises.

So, being able to run Logic Apps on that sounds like a good idea, right? However, there’s more to it than that, so there might be some cases where this is a really good thing to do. For example, if you’ve already made an investment in Kubernetes clusters, then that might seem like a logical extension of what to do, particularly if you’ve assigned compute for that and you want to reuse that compute at no additional cost. The other thing is if you need to be running your workloads close to other resources, so for example, you don’t have a fast network link to the cloud and you need to talk to applications there, then that can really make sense because you can spin up even a small Kubernetes cluster, have it remote at the edge, but still reap the benefits of Logic Apps there. Similarly, there are other regulatory considerations.

So, a client of ours, for example, needs to be able to run with no Internet connection for a predetermined period of time, which means that we can’t always rely on having things in the cloud. However, if you’ve deployed to a local Kubernetes cluster from Azure Arc and that link gets severed, this will continue to run. So that meets the regulatory requirement. However, there are issues as well, because particularly this isn’t currently generally available. So although this is in preview, you can’t use this now for solutions that you’re going to release straight away.

Great for the future, great if you’ve already got an investment in Kubernetes. But Kubernetes is not a simple thing that you just decide to do on a whim. You need to plan that properly. We can help you with that. However, what we currently do for Logic Apps’ standard runtime is we’ll put them on an App Service hosting plan.

Now, this also has a lot of benefits. It’s really easy to deploy because it’s Platform as a Service, it looks after itself, it’s easy to manage, you don’t need to do anything. Azure looks after it for you. This is currently generally available. So, you can deploy this today and it’s fully supported, and also it’s cost-effective even at a very small scale.

One of the things we’ve found with Kubernetes is if you’ve got big workloads or big scale, that’s where it really hits the sweet spot. However, if you’ve got fairly small workloads or you’re going to start small and get big later, then this is definitely the right way to go. So, there’s no definite right or wrong answer. You just need to know what it is that you’re trying to get out of it and then choose the appropriate technology based on that.

Chat to us about your Integration journey

Get in touch

Share this post