Update auto-deploy-image to v0.15.0
What does this MR do?
This brings an ugpraded PostgreSQL chart to Auto DevOps deployments by default. With this change, Auto DevOps supports Kubernetes 1.16+ out of the box.
It is a breaking change in that deployments using the old chart will fail until users either opt back into the old chart by setting AUTO_DEVOPS_POSTGRES_CHANNEL to 1 or upgrade their in-cluster database. The deployment fails with a descriptive message explaining exactly why it is failing and how to resolve it.
In order to enable this upgrade, we have to move POSTGRES_VERSION out of the top-level Auto DevOps template. This is to allow the default version to vary based on the selected AUTO_DEVOPS_POSTGRES_CHANNEL.
See gitlab-org/cluster-integration/auto-deploy-image@v0.14.0...v0.15.0 for the changes to the image
See #210499 (closed) for context on the change
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team