Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • Requirements
    • Requirements
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !24789

Merged
Created Jan 30, 2019 by Thong Kuah@tkuahMaintainer12 of 13 tasks completed12/13 tasks

Upgrade cluster applications, starting with runner

  • Overview 61
  • Commits 8
  • Pipelines 18
  • Changes 39

What does this MR do?

  1. Adds ability to upgrade cluster applications

Re-uses the same services used to install a cluster application to also upgrade a cluster application. This is possible as helm allows installation and upgrade to both use helm upgrade --install.

This allows for the following new transitions:

  • a successful upgrade: installed -> scheduled -> updating -> installed updated
  • a failed upgrade: installed -> scheduled -> updating -> update_errored.

cf. successful installation is installable -> scheduled -> installing -> installed.

  1. Allow in the Frontend to upgrade the runner application

Other changes:

  • Changes InstallCommand to use helm upgrade --install.
  • Adds Clusters::Application::UpgradeService where the state transition needed to be scheduled -> updating.

What are the relevant issue numbers?

  • https://gitlab.com/gitlab-org/gitlab-ce/issues/49384
  • https://gitlab.com/gitlab-org/gitlab-ce/issues/56524

Tasks

  • Only allow upgrades if version != VERSION ?
  • [-] Show what version was attempted in error message ?
  • Test new transitions
  • Update version column after update complete - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24810

Manual QA test

  • Install runner
  • Upgrade runner via UI (re-enabled Install button via Chrome Dev tools and hit button)
  • Upgrade runner via rails console - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24789#note_136426318
  • Check Prometheus alerts still works - https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9483#note_139063962

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • [-] Documentation created/updated via this MR
  • [-] Documentation reviewed by technical writer or follow-up review issue created
  • Tests added for this feature/bug
  • [-] Tested in all supported browsers
  • Conforms to the code review guidelines
  • Conforms to the merge request performance guidelines
  • Conforms to the style guides
  • [-] Conforms to the database guides
  • [-] Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
  • Security reports checked/validated by reviewer
Edited Feb 07, 2019 by Thong Kuah
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: use_upgrade_install_for_helm_apps

Enable Gitpod?

To use Gitpod you must first enable the feature in the integrations section of your user preferences.

Cancel Enable Gitpod