Learning Library

← Back to Library

Accelerating Cloud Migration with Kubernetes and Service Mesh

Key Points

  • The team progressed from bare‑metal servers to virtualized instances and finally to Kubernetes, which now orchestrates roughly 40 microservices and would have been unmanageable without it.
  • Shifting configuration and pipeline responsibilities to developers created a synergy that reduced operational overhead, letting developers build Docker images locally that match what is deployed in the cloud.
  • Managed Kubernetes enables rapid provisioning of isolated environments—clusters can be spun up in minutes or a full data‑center in 24 hours—allowing teams to test and develop without affecting each other.
  • Adopting the Sto service mesh added security and automatic HTTP retry logic without code changes, and the overall cloud strategy has accelerated delivery, improved visibility, and enhanced SLA performance while effectively amplifying the team’s capacity.

Full Transcript

# Accelerating Cloud Migration with Kubernetes and Service Mesh **Source:** [https://www.youtube.com/watch?v=c_N0I4ffHcA](https://www.youtube.com/watch?v=c_N0I4ffHcA) **Duration:** 00:02:37 ## Summary - The team progressed from bare‑metal servers to virtualized instances and finally to Kubernetes, which now orchestrates roughly 40 microservices and would have been unmanageable without it. - Shifting configuration and pipeline responsibilities to developers created a synergy that reduced operational overhead, letting developers build Docker images locally that match what is deployed in the cloud. - Managed Kubernetes enables rapid provisioning of isolated environments—clusters can be spun up in minutes or a full data‑center in 24 hours—allowing teams to test and develop without affecting each other. - Adopting the Sto service mesh added security and automatic HTTP retry logic without code changes, and the overall cloud strategy has accelerated delivery, improved visibility, and enhanced SLA performance while effectively amplifying the team’s capacity. ## Sections - [00:00:00](https://www.youtube.com/watch?v=c_N0I4ffHcA&t=0s) **From Bare‑Metal to Dev‑Driven Kubernetes** - The team migrated from bare‑metal servers to virtual machines and then to Kubernetes, enabling 40 microservices, shifting configuration responsibility to developers, and dramatically accelerating environment provisioning and operational efficiency. ## Full Transcript
0:03our cloud journey started with 0:06bare-metal services for everything we 0:07started off by migrating services to 0:09what's called via size virtualized 0:12instances after that we made the journey 0:14over to kubernetes we have almost 40 0:16micro services under our belt and 0:18kubernetes helps us orchestrate and 0:21manage those services moving to a micro 0:24services architecture without kubernetes 0:27would have been a nightmare the amount 0:30of manpower required to maintain and 0:33service that infrastructure would be 0:36magnitudes higher than we currently have 0:38in terms of our staff as we switched to 0:40kubernetes what happened was the 0:42developers began to take control of how 0:45applications were configured and how 0:46pipelines were built out that actually 0:48gave us a lot of efficiencies because it 0:50took workload off of the operations 0:52teams plate and it put it on to the 0:55developers plate which actually created 0:58a synergy and that synergy was that 1:00instead of us having to rely on a 1:04separate team to do configuration 1:06management the developers were able to 1:09figure out what that app needed in terms 1:11of resources and they can build their 1:13own docker files and what they ran 1:15locally on their machine was what was 1:17deployed out to the cloud with manage 1:19kubernetes we've been able to create 1:21environments within minutes we can build 1:23up a new cluster we can configure it and 1:26we can give a team that needs an 1:29integration environment the services 1:31they need and in isolated region we can 1:34continue our work as a development team 1:36on building other features or our 1:38customers require so we can break things 1:41without the fear that we're tearing up 1:43someone else's integration environment 1:45that's some functionality that we never 1:48had before kubernetes has greatly 1:50improved our velocity in terms of 1:52spinning up data centers what used to 1:54take us a month to spend up an entire 1:56data center we can now do within 24 1:58hours steel house chose Sto as our 2:01service mesh for several reasons the 2:02security that it provides and the 2:04ability to do retry logic on HTTP 2:06requests sto providing retry logic 2:09without us having to modify our code is 2:12a huge benefit 2:13the big benefits we've seen from our 2:15cloud strategy have been our abilities 2:16to move faster develop and deploy 2:19quicker and have better insight into our 2:21applications and to do all this with a 2:24better SLA because we were able to 2:27leverage our cloud providers manage 2:29services that allows our team to seem 2:31bigger than it is 2:35you