Home / Companies / GitLab / Blog / Post Details
Content Deep Dive

How to keep GitLab Auto DevOps and Managed Apps working after Helm stable repo is removed

Blog post from GitLab

Post Details
Company
Date Published
Author
Thong Kuah
Word Count
447
Company Posts That Month
21
Language
English
Hacker News Points
-
Summary

The removal of the Helm Stable repository on November 13 affects GitLab's Auto DevOps and Managed Apps, causing potential deployment failures due to the inability to fetch the repository. To mitigate these issues, GitLab has introduced a Helm Stable Archive repository and recommends users upgrade to GitLab versions 13.5 or later, specifically 13.6 when released, or use newer versions of specific images in their .gitlab-ci.yml files. Users not utilizing Helm with Kubernetes in Auto DevOps, such as those deploying to AWS, will not be impacted. Additionally, GitLab has addressed the installation failures for Managed Apps like Ingress, Fluentd, Prometheus, and Sentry by switching to the Helm Stable Archive repository in GitLab 13.5.0 and later versions. Applications not hosted in the Helm Stable repository, such as GitLab Runner, remain unaffected by these changes.

Trends Found in this Post

No tracked trend matches for this post yet.