-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18.0, 4.19, 4.20
-
None
-
None
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Instructions includes unnecessary nested spec element
Version-Release number of selected component (if applicable):
How reproducible:
Easy
Steps to Reproduce:
1. Follow instructions here: https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/security_and_compliance/cert-manager-operator-for-red-hat-openshift#cert-manager-install-cli_cert-manager-operator-install
2. For cert-manager Operator for Red Hat OpenShift v1.15.0 or later, create a YAML file with the following content:
3. operatorgroup api definition does not define nested spec element operatorgroup.spec.spec - can be validated with "oc explain operatorgroup.spec"-command
Actual results:
It works in general but if deploying Cert-Manager using ArgoCD status will be out of sync because desired manifest and live manifest are not matching 100% since ArgoCD is expecting to meet requirement operatorgroup.spec.spec which does not exist.
Expected results:
Additional info: