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

Share :
comments powered by Disqus

Related Posts

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