Achieve a smaller blast radius with Highly Available Kubernetes clusters

  • twitter
  • linkedin
  • facebook
  • email

Kubernetes is integral to our operations, allowing us to serve 60,000 requests per second to 20 customers across 30 clusters. In order to deliver an optimised service, we built SCHIP, a specialised multi-tenant Kubernetes distribution that extends and enhances the vanilla distribution.

By Tanat Paul Lokejaroenlarb

At the same time, we wanted to increase the resilience and redundancy of our platform, allowing us to easily redirect traffic between clusters to maintain a quality service should one degrade or we needed to perform risky maintenance and upgrades. We called this ‘reducing the blast radius’.

Read our latest article to discover:

  • How to use Weighted records in AWS Route 53 to control traffic flow between clusters.
  • How to build a traffic controller to automatically direct traffic to clusters using Weighted records info.
  • How the traffic controller also monitors Kubernetes pod health to update Weighted records and automate traffic redirection.

The new traffic operator allows us to grow and evolve the SCHIP platform for future success – without affecting service availability or performance. Read the Adevinta blog for full details of what we did and what was achieved.

Our jobs

View all our jobs

More resources

Discover our media resources, brand assets, guidelines, photos and more