Renew the Auto Deploy stable template by the latest template [RUN ALL RSPEC] [RUN AS-IF-FOSS]
What does this MR do?
This MR renews the Auto Deploy stable template by the latest template, that was announced as a 14.0 breaking change a few months ago (Also, re-announced in the recent blogpost). You can see this issue about the full details of this change.
The stable template renewal has already been rolled out via the feature flag.
related #232788 (closed)
Troubleshooting
Basically, all of the upgrade/troubleshooting information are described in the upgrade guide. When a user encountered a problem, they should either:
- [RECOMMENDED] Upgrade the Kubernetes instance according to the guidance, OR
- Use a legacy version of Auto Deploy dependencies. You can also use this Auto DevOps 13.12 archived project.
The information is also surfaced in the job log.
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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