You need to sign in or sign up before continuing.
Migrations for Operator SDK 1.32.0
What does this MR do?
Migrations for Operator SDK 1.32.0
Upgrade the tool version of the Operator SDK and apply the following
migrations:
- Add annotation to specify the default container:
https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.16.0/#add-annotation-to-specify-the-default-container
- Reduce debug log level for the sidecar container kube-rbac-proxy
from 10 to 0:
https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.17.0/#reduce-debug-log-level-for-the-sidecar-container-kube-rbac-proxy-from-10-to-0
- Add resource requests and limits to kube-rbac-proxy:
https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.17.0/#add-resource-requests-and-limits-to-kube-rbac-proxy
The new RBAC proxy container resources can be controlled with
`.manager.kubeRbacProxy.ressources`.
Changelog: changed
The Operator SDK version of the build image will be bumped in gitlab-org/gitlab-build-images!741 (merged).
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
Merge Request Title and Description are up to date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline on GitLab.com -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes -
Documentation created/updated -
Tests added -
Integration tests added to GitLab QA -
Equivalent MR/issue for omnibus-gitlab opened -
Validate potential values for new configuration settings. Formats such as integer10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.
Related issues
Closes #603 (closed)
Edited by Hossein Pursultani