There are some complains that we can share, but honestly they are not really that fun to read. We are still early in our transition and one major complaint I have is about helm and lack of flexibility of it and operator…
> Wrong. Actual analysis by the engineers of one of their migrated jobs (urgent-other sidekiq shard) says their cost went from $290/month when running in VMs to $700/month when running in Kubernetes. This is only one of…
> yet when they just dip their toes into kubernetes world, when they switched their docker image registry to run on kube, they've quickly discovered glaring omissions like missing liveness probe and storm of errors on…
GitLab.com is using the omnibus-gitlab package and it is configured in the HA configuration as per docs in https://docs.gitlab.com/ee/administration/high_availability/... . The actual update is being done using the…
I work for GitLab and I was responsible for introducing release changes for this cycle. That is correct, we deploy our RCs to production. I consider RC as only a point in time snapshot of a release that will be sent to…
There are some complains that we can share, but honestly they are not really that fun to read. We are still early in our transition and one major complaint I have is about helm and lack of flexibility of it and operator…
> Wrong. Actual analysis by the engineers of one of their migrated jobs (urgent-other sidekiq shard) says their cost went from $290/month when running in VMs to $700/month when running in Kubernetes. This is only one of…
> yet when they just dip their toes into kubernetes world, when they switched their docker image registry to run on kube, they've quickly discovered glaring omissions like missing liveness probe and storm of errors on…
GitLab.com is using the omnibus-gitlab package and it is configured in the HA configuration as per docs in https://docs.gitlab.com/ee/administration/high_availability/... . The actual update is being done using the…
I work for GitLab and I was responsible for introducing release changes for this cycle. That is correct, we deploy our RCs to production. I consider RC as only a point in time snapshot of a release that will be sent to…