Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A autodeploy-service
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

We are happy to announce the rollout of GitLab 15.0 in July! 🥳 Please check the information on breaking changes and feature removals to determine if your workflows are impacted.

  • memoriav
  • Memobase 2020
  • services
  • autodeploy-service
  • Issues
  • #1

Closed
Open
Created Aug 24, 2021 by Sebastian Schüpbach@sschuepbachOwner

End support for directly deploying k8s manifests

At the moment, the autodeploy service comprises two distinct ways for deploying applications:

  • With kubectl and by using the manifests inside the k8s-manifests directory
  • With helm and by using the charts inside the helm-charts directory

I recommend to end the support for the former way because of the following reasons:

  • As far as I know, all services in the Memobase project have moved to the "Helm way" (@jonas.waeber , @edelmatthias , @guenter.hipler , @lionel.walter, do you agree?)
  • We could speed up the deployment process because the cloning of the repository, which is required to decide if the project is deployed via helm or via kubectl, would not be necessary anymore.
  • The deployment process in the code is possibly buggy: As of now, all manifests inside the k8s-manifests/test path are deployed, but only k8s deployment objects are deleted beforehand.
Assignee
Assign to
Time tracking