Tracked topic
DevOps is a data-driven practice, so the idea of setting limits to conserve resources without any underlying data about what users are doing can seem counterintuitive. If you’re migrating to Kubernetes runners from a Docker runner or a shell runner, it’s easy enough to extrapolate the numbers to establish limits as you set up your Kuberntes runners. If you’re brand-new to GitLab and GitLab CI, then it’s kind of a shot in the dark. Think about your bills and resource constraints: How much memory and CPU is available? Is anything else running on your K8s cluster. Chances are, your guesses will b
Best practices to keep your Kubernetes runners moving…Photo by David Clode on Unsplash More to explore DevSecOps Consolidate your GitLab stack with Gitaly on Kubernetes DevSecOps Teaching software development the easy way using GitLab DevSecOps AI is reshaping DevSecOps…
…In addition to our Kubernetes-native integrations and multicloud deployment support, we’ve added Feature Flags , an Operations Dashboard , and will release Incident Management in 12.1. With GitLab 12.0, releasing…
…More to explore DevSecOps Consolidate your GitLab stack with Gitaly on Kubernetes DevSecOps Teaching software development the easy way using GitLab DevSecOps AI is reshaping DevSecOps: Attend GitLab Transcend to see what…
To show you the most relevant results, we’ve omitted some entries very similar to those already shown. Repeat the search with the omitted results included.