Are you sure you know what is happening in your GitLab Runners? GitLab CI is extremely powerful and flexible, however with that users can easily make mistakes that could take out a GitLab Runner, and potentially clog up Sidekiq bringing your entire GitLab instance to it’s knees. In this talk, Senior Software Engineer Sean Smith discusses some situations that F5 Networks ran into in their installation, for example CI jobs growing exponentially; as well as how monitoring was implemented after incidents occurred and how to limit the impact of incidents when they occur.
Top comments (0)