Nov 9, 2020 - Thong Kuah    

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

The Helm stable repository will be removed this month. We explain how to keep Auto DevOps and GitLab Managed Apps working.

The Helm project announced that the Helm Stable repository will be removed on November 13. This change impacts GitLab Auto DevOps and GitLab Managed Apps.

How Auto DevOps is impacted

Removing the Helm stable repository affects Auto Deploy and Auto Review Apps stages of Auto DevOps. The deploy jobs from these stages will fail because they cannot fetch the Helm stable repository. GitLab has mitigated this in GitLab 13.6 by switching to a Helm Stable Archive repository maintained by GitLab.

In case Auto DevOps pipelines are failing because of this problem, you can:

  1. Upgrade to GitLab 13.6.0 when it is released, or
  2. If you are on GitLab 13.5.X, you can also upgrade to GitLab 13.5.3
  3. If you are on GitLab 13.4.X, you can also upgrade to GitLab 13.4.6
  4. Specify a newer version of the auto-deploy-image image, which contains the fix, in your .gitlab-ci.yml file:

     include:
       - template: Auto-DevOps.gitlab-ci.yml
    
     .auto-deploy:
       image: "registry.gitlab.com/gitlab-org/cluster-integration/auto-deploy-image:v1.0.7"
    

Not all users will be affected by the change. Users who are not using Helm as part of Auto DevOps, for example, those that are not using Kubernetes (Auto Deploy to AWS targets) will not be impacted by the removal of the Helm stable respository.

How GitLab managed apps are impacted

The removal of the Helm stable repository affects installation of the Ingress, Fluentd, Prometheus, and Sentry apps. These apps will fail to install as the Helm stable repository is removed. For the following:

GitLab Managed Apps: GitLab has mitigated this problem in GitLab 13.5.0 by switching to a Helm Stable Archive repository maintained by GitLab.

There are a few ways to fix app installation failures because of the Helm stable repository was removed.

  1. Upgrade to GitLab 13.5.0 or later, or
  2. If you are on GitLab 13.4.X, you can also upgrade to GitLab 13.4.6.
  3. If you are on GitLab 13.3.X, you can also upgrade to GitLab 13.3.8.

GitLab has mitigated the problem in GitLab 13.6 for users with GitLab Managed Apps using CI/CD by switching to a Helm Stable Archive repository maintained by GitLab.

In case GitLab Managed Apps CI/CD installation pipelines are failing because of this problem, you can:

  1. Upgrade to GitLab 13.6.0 when it is released, or
  2. Specify a newer version of the cluster-applications image, which contains the fix, in your .gitlab-ci.yml file:

     include:
       - template: Managed-Cluster-Applications.gitlab-ci.yml
    
     apply:
       image: "registry.gitlab.com/gitlab-org/cluster-integration/cluster-applications:v0.34.1"
    

If you are installing applications that were not hosted in the Helm stable repository such as GitLab Runner, these applications will not be affected.

Learn more about the project

Cover image by Maximilian Weisbecker on Unsplash

Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license