What we learned after a year of GitLab.com on Kubernetes

What we learned after a year of GitLab.com on Kubernetes

  • September 17, 2020
Table of Contents

What we learned after a year of GitLab.com on Kubernetes

It’s been one year since we moved GitLab.com to Kubernetes. We unpack the challenges and learnings from this major migration. For about a year now, the infrastructure department has been working on migrating all services that run on GitLab.com to Kubernetes.

The effort has not been without challenges, not only with moving services to Kubernetes but also managing a hybrid deployment during the transition. We have learned a number of lessons along the way that we will explore in this post.

Source: gitlab.com

Tags :
Share :
comments powered by Disqus

Related Posts

Building a Kubernetes platform at Pinterest

Building a Kubernetes platform at Pinterest

Over the years, 300 million Pinners have saved more than 200 billion Pins on Pinterest across more than 4 billion boards. To serve this vast user base and content pool, we’ve developed thousands of services, ranging from microservices of a handful CPUs to huge monolithic services that occupy a whole VM fleet. There are also various kinds of batch jobs from all kinds of different frameworks, which can be CPU, memory or I/O intensive.

Read More
Introducing PodTopologySpread

Introducing PodTopologySpread

Managing Pods distribution across a cluster is hard. The well-known Kubernetes features for Pod affinity and anti-affinity, allow some control of Pod placement in different topologies. However, these features only resolve part of Pods distribution use cases: either place unlimited Pods to a single topology, or disallow two Pods to co-locate in the same topology.

Read More
What’s new in Kubernetes 1.16?

What’s new in Kubernetes 1.16?

What’s new in Kubernetes 1.16: Ephemeral containers for easy pod debugging, support for dual-stack network, new options for the scheduler and much more. These are the features that look more exciting to us for this release (ymmv): Ephemeral containers are a great way to debug running pods, as you can’t add regular containers to a pod after creation (you should use sysdig tools like kubectl capture or kubectl trace for that though!), but you can run ephemeral containers. Right now the steps to run an ephemeral container aren’t straightforward.

Read More