Situation at a glance
- Industry: healthcare technology, with digital services carrying sensitive operational expectations.
- Platform decision: use AKS where container orchestration and scaling were justified.
- Delivery model: automate builds, image storage, and deployments through GitLab pipelines.
Context and healthcare platform pressure
Core points
- The team needed digital services that could scale with demand while meeting healthcare-grade security and availability expectations.
- Manual deployment paths increased operational risk as workloads and environments grew.
- The platform needed a clearer AWS Managed Platform path where infrastructure, release, and security controls moved together.
AKS architecture and delivery choices
Core points
- Azure Kubernetes Service provided the container platform for scalable service hosting.
- GitLab Cloud, GitLab container registry, and CI/CD pipelines handled image build, storage, and deployment automation.
- Security expectations aligned with AWS Zero Trust Security principles, including controlled access and repeatable deployment evidence.
Delivery milestones and operating controls
Core points
- The platform was provisioned around workload scalability, reliability, and security needs.
- Container deployment became repeatable instead of dependent on manual steps.
- Release control and infrastructure ownership became clearer for the technical team.
Skunk tip
- Make deployment automation part of the platform acceptance criteria, not a later optimisation task.
Measured outcomes and lessons
Core points
- The team gained a stronger foundation for scaling healthcare digital services.
- Security and release routines became easier to explain and repeat.
- The main lesson is that Azure partner services work creates confidence when platform design and deployment automation are planned together.
A Kubernetes cluster is only useful when release flow, access control, and support ownership are designed with it.
