Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • See what's new at GitLab
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
A
auto-deploy-app
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39
    • Issues 39
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issues
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • charts
  • auto-deploy-app
  • Issues
  • #47

Closed
Open
Opened Feb 14, 2020 by Thong Kuah@tkuah
  • Report abuse
  • New issue
Report abuse New issue

Change default for deploymentApiVersion to `apps/v1` (breaking change)

Proposal

In Auto DevOps, switch default of deploymentApiVersion: extensions/v1beta1 to new default deploymentApiVersion: apps/v1. Switch planned for GitLab %13.0

Impact

If user is using Kubernetes 1.9 and below, they will need to upgrade their Kubernetes cluster in order to get apps/v1. Note in https://docs.gitlab.com/ee/topics/autodevops/#requirements, we require Kubernetes 1.12+

If the user's cluster is Kubernetes 1.9 or below, this breaking change will cause them to an error message like:

unable to find resource of type 'deployment'

Impact on GitLab.com

As there should be minimal number of users using Kubernetes 1.9 or below, it should be OK to deploy to GitLab.com whenever this change is ready

Background

In gitlab-org/gitlab#32720 (closed), we added support for changing deploymentApiVersion. The ability to use deploymentApiVersion: apps/v1 has been available since Kubernetes 1.9. Kubernetes 1.16 no longer will be serving extensions/v1beta1 deployments.

/cc @danielgruesso @nicholasklick

Edited Apr 30, 2020 by Thong Kuah

Linked issues

  • Discussion
  • Designs
Assignee
Assign to
13.0
Milestone
13.0
Assign milestone
Time tracking
None
Due date
None
6
Labels
Category:Auto DevOps Deliverable breaking change devopsconfigure groupconfigure workflowIn review
Assign labels
  • View project labels
Reference: gitlab-org/charts/auto-deploy-app#47