Closed Fedosin closed 1 month ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from fedosin. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Name | Link |
---|---|
Latest commit | b4de99600d13ef8665345f909dce2919acb88f37 |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-cluster-api-operator/deploys/6633a81c5897d900092c2f68 |
Deploy Preview | https://deploy-preview-515--kubernetes-sigs-cluster-api-operator.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
During the community meeting we decided to remove cert-manager support from the helm chart, because it is doesn't work with ArgoCD.
This reverts commit c8a9022ba90e00c259ef5a8c4ca6a69d69180ed4.
What this PR does / why we need it:
PR #453 broke installation of cert-manager CRDs, so we revert that regression.
The reason why cert-manager CRDs were placed in "crds" folder, is because in this case Helm applies them earlier, before all other manifests. Also Helm guarantees that if these CRDs are already presented in the system, it won't overwrite them.
If we template everything together, both cert-manager resources and CRDs will be applied simultaneously, and we get this error:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #