Register to build your agenda.

(DeveloperWeek): How to Avoid 'Day 2' Kubernetes Problems

DeveloperWeek PRO Stage B
Join on Hopin

Lewis Marshall, SRE and Tech Evangelist

Lewis Marshall is an SRE and Tech Evangelist ( With 28 years of software and infrastructure experience; I've worked my way from x86 Assembly all the way to Golang and Kubernetes. Also a space geek on a OneWheel.

In this session, Lewis Marshall from Appvia, will discuss best practice for teams managing the critical 'Day-2' phase of Kubernetes deployments, and the key areas they must have visibility and coverage on -production topology, updating, monitoring, scaling.

Day-2 is the time between the initial deployment of a cluster for development and when kubernetes clusters are hosting a production business service. It sits between designing the deployment (Day-1), and ongoing maintenance (Day-3)

Moving from Day 1 to Day 2 isn't as simple as it might seem. It's a critical time period where you bring technology out of the development staging phase and into production. Without a solid plan to overcome the traps along the way, you won't be able to realise the potential benefits of Kubernetes, you'll struggle to scale your environments and put the entire infrastructure in danger.

Key points Lewis will cover include what best practice looks like and his own experience of deploying Kubernetes for major organisations (including in the UK's Home Office).

We discuss how the business service requirements are affected when running on Kubernetes:

Production Topology - How isolation of workloads, clusters and cloud resources e.g. networking, affects all other day two concerns.
Upgrading - the choice a team makes around upgrading is essential to making sure there's no downtime to hosted applications within your cluster.
Monitoring - the business drivers around actual service availability and support and how Kubernetes helps and hinders observability.