Back to Tech landscape

Kubernetes

Cloud & DevOps

Orchestrate microservices on AKS with Helm and observability

Official documentation (opens in a new tab)

Overview

Kubernetes—primarily Azure Kubernetes Service (AKS)—hosts ConnectSoft microservice estates when programs need fine-grained scaling, service mesh patterns, or multi-team cluster sharing. Factory delivery includes Helm charts, ingress with TLS, liveness probes, and resource quotas aligned to .NET 10 service footprints.

We integrate Prometheus scraping, OpenTelemetry collectors, and cluster-level logging so platform operators see node and pod health alongside Application Insights application traces. GitOps or pipeline-driven upgrades keep cluster drift visible and reversible.

Docker images built in Azure DevOps promote unchanged into Kubernetes—no rebuild surprises between environments. For smaller footprints, Container Apps may suffice; we choose AKS when operational requirements justify cluster ownership.

Scaling a .NET platform beyond single-host limits on Azure? Kubernetes in our playbook pairs with the same containers and pipelines you already use locally.

Why we use it:

  • AKS as the primary Kubernetes target for Factory microservice estates
  • Helm charts with environment-specific values and secrets stores
  • Ingress, TLS, and health probes for ASP.NET Core services
  • Prometheus and OpenTelemetry integration for cluster and app metrics
  • Pipeline-driven deploys from the same Docker images used in dev
  • Right-sized choice versus Azure Container Apps for smaller programs

Ready to work with us?

Let's discuss how our team can help achieve your digital goals