Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 215
    • Issues 215
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #250
Closed
Open
Issue created Jan 14, 2020 by Adam Fekete@afeketeOwner

Updating Helm 3 on the cluster

The main goal of this issue to discuss the switching to Helm 3 in the near future. The main advantages of the new version are that it doesn't use tiller and there is no separate user management anymore. So it should be more simple and secure. The new version depends on the kubernetes API only. I'm not an expert in this field, but this is how I can interpret the changes.

Note: This is a major version update so it can break things!

Currently, the version of the Helm is fixed to v2.14.3. Accordingly in the configuration of gitlab-ci yml file the image: dtzar/helm-kubectl:2.14.3 should be used. To prevent any modification of tiller the helm init --upgrade command should be avoided.

Possible issues:

  • The old deployments are not available after updating Helm. So it looks like that each deployment require a "clean start".
  • In theory, the charts are backwards compatible they must be tested before switching to the new version
Assignee
Assign to
Time tracking