Projects QA

Following the packages and its finding(s) obtained by checking the image and the bundle manifests distributed on it. This report aims to try to identify some define QA criteria for the packages. Note that only the head of channels are checked which means that this report has the purpose the evaluate the latest distributions only.

Data from the image used

Image name: registry.redhat.io/redhat/redhat-operator-index:v4.11
Image ID: sha256:6ca7d522474984a8c16ac436ddb5d8ad9418fd75d668c285e0e08995eec0e956
Image Created at: 2022-09-02T22:52:24.087536
From JSON report generated at: 2022-09-17

Projects QA

Package Name	Channel Naming	Disconnect Annotation	Scorecard	Validators	Capability level	Subscriptions (From default channel)	Potently impacted by removals on K8S 1.25/1.26	SDK	Custom Scorecard
sandboxed-containers-operator	NOT COMPLY Following those does NOT complies: (+) . preview-1.1 preview-1.0 Following those complies: stable-1.2 stable-1.3	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For sandboxed-containers-operator.v1.1.0: Owned CRDs do not have resources specified error spec does not exist for the custom resource example-kataconfig kataconfigs.kataconfiguration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example-kataconfig] For sandboxed-containers-operator.v1.2.2: error spec does not exist for the custom resource example-kataconfig Owned CRDs do not have resources specified kataconfigs.kataconfiguration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example-kataconfig] For sandboxed-containers-operator.v1.0.2: error spec does not exist for the custom resource example-kataconfig Owned CRDs do not have resources specified spec missing from [example-kataconfig] kataconfigs.kataconfiguration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For sandboxed-containers-operator.v1.3.0: Owned CRDs do not have resources specified error spec does not exist for the custom resource example-kataconfig kataconfigs.kataconfiguration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example-kataconfig]	CHECK THE WARNINGS (+) For sandboxed-containers-operator.v1.1.0: Warning: Value sandboxed-containers-operator.v1.1.0: channel(s) ["preview-1.1"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (sandboxed-containers-operator.v1.1.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For sandboxed-containers-operator.v1.2.2: Warning: Value : (sandboxed-containers-operator.v1.2.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For sandboxed-containers-operator.v1.0.2: Warning: Value sandboxed-containers-operator.v1.0.2: channel(s) ["preview-1.0"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (sandboxed-containers-operator.v1.0.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For sandboxed-containers-operator.v1.3.0: Warning: Value : (sandboxed-containers-operator.v1.3.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	Seamless Upgrades Basic Install [Seamless Upgrades Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): node.k8s.io/runtimeclasses (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
skupper-operator	NOT COMPLY Following those does NOT complies: (+) . alpha	SHOULD SUPPORT	PASSED IN ALL CHECKS	CHECK THE WARNINGS (+) For skupper-operator.v1.0.5: Warning: Value skupper-operator.v1.0.5: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value skupper-operator.v1.0.5: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (skupper-operator.v1.0.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"Red Hat Application Interconnect"		USED	NOT USED
container-security-operator	NOT COMPLY Following those does NOT complies: (+) . quay-v3.5 quay-v3.4 Following those complies: stable-3.7 stable-3.6	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For container-security-operator.v3.5.7: features does not have a spec descriptor image does not have a spec descriptor manifest does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for features Add a spec descriptor for image Add a spec descriptor for manifest imagemanifestvulns.secscan.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For container-security-operator.v3.4.7: error spec does not exist for the custom resource sha256.a7b23f38d1e5be975a6b516739689673011bdfa59a7158dc6ca36cefae169c18 Owned CRDs do not have resources specified spec missing from [sha256.a7b23f38d1e5be975a6b516739689673011bdfa59a7158dc6ca36cefae169c18] imagemanifestvulns.secscan.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For container-security-operator.v3.7.8: Owned CRDs do not have resources specified Warning: Value : (container-security-operator.v3.7.8) example annotations not found For container-security-operator.v3.6.10: Owned CRDs do not have resources specified Warning: Value : (container-security-operator.v3.6.10) example annotations not found	CHECK THE WARNINGS (+) For container-security-operator.v3.5.7: Warning: Value container-security-operator.v3.5.7: unable to find the resource requests for the container: (container-security-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value container-security-operator.v3.5.7: channel(s) ["quay-v3.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (container-security-operator.v3.5.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For container-security-operator.v3.4.7: Warning: Value container-security-operator.v3.4.7: unable to find the resource requests for the container: (container-security-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value container-security-operator.v3.4.7: channel(s) ["quay-v3.4"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (container-security-operator.v3.4.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For container-security-operator.v3.7.8: Warning: Value container-security-operator.v3.7.8: unable to find the resource requests for the container: (container-security-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (container-security-operator.v3.7.8) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value : (container-security-operator.v3.7.8) example annotations not found For container-security-operator.v3.6.10: Warning: Value container-security-operator.v3.6.10: unable to find the resource requests for the container: (container-security-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (container-security-operator.v3.6.10) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value : (container-security-operator.v3.6.10) example annotations not found	[Full Lifecycle]	"OpenShift Platform Plus" "Red Hat Quay"		NOT USED	NOT USED
local-storage-operator	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For local-storage-operator.4.11.0-202208291725: Owned CRDs do not have resources specified maxDeviceCount does not have a spec descriptor Add a spec descriptor for maxDeviceCount Warning: Value local.storage.openshift.io/v1alpha1, Kind=LocalVolumeDiscoveryResult: provided API should have an example annotation localvolumes.local.storage.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status localvolumesets.local.storage.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status localvolumediscoveries.local.storage.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For local-storage-operator.4.11.0-202208291725: Warning: Value local-storage-operator.4.11.0-202208291725: csv.metadata.Name local-storage-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value local.storage.openshift.io/v1alpha1, Kind=LocalVolumeDiscoveryResult: provided API should have an example annotation	[Full Lifecycle]	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
red-hat-camel-k	NOT COMPLY Following those does NOT complies: (+) . 1.8.x latest 1.4.x 1.6.x Following those complies: candidate stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For red-hat-camel-k-operator.v1.8.0: integrationplatforms.camel.apache.org does not have a status descriptor flows does not have a spec descriptor kamelet does not have a spec descriptor profile does not have a spec descriptor resources does not have a spec descriptor build does not have a spec descriptor definition does not have a spec descriptor flow does not have a spec descriptor sink does not have a spec descriptor source does not have a spec descriptor Owned CRDs do not have resources specified builds.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status camelcatalogs.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrations.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationkits.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd integrationplatforms.camel.apache.org. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ kamelets.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kameletbindings.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for flows Add a spec descriptor for kamelet Add a spec descriptor for profile Add a spec descriptor for resources Add a spec descriptor for build Add a spec descriptor for definition Add a spec descriptor for flow Add a spec descriptor for sink Add a spec descriptor for source For red-hat-camel-k-operator.v1.8.0: integrationplatforms.camel.apache.org does not have a status descriptor flows does not have a spec descriptor kamelet does not have a spec descriptor profile does not have a spec descriptor resources does not have a spec descriptor build does not have a spec descriptor definition does not have a spec descriptor flow does not have a spec descriptor sink does not have a spec descriptor source does not have a spec descriptor Owned CRDs do not have resources specified builds.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status camelcatalogs.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrations.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationkits.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd integrationplatforms.camel.apache.org. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ kamelets.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kameletbindings.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for flows Add a spec descriptor for kamelet Add a spec descriptor for profile Add a spec descriptor for resources Add a spec descriptor for build Add a spec descriptor for definition Add a spec descriptor for flow Add a spec descriptor for sink Add a spec descriptor for source For red-hat-camel-k-operator.v1.8.0: integrationplatforms.camel.apache.org does not have a status descriptor flows does not have a spec descriptor kamelet does not have a spec descriptor profile does not have a spec descriptor resources does not have a spec descriptor build does not have a spec descriptor definition does not have a spec descriptor flow does not have a spec descriptor sink does not have a spec descriptor source does not have a spec descriptor Owned CRDs do not have resources specified builds.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status camelcatalogs.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrations.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationkits.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd integrationplatforms.camel.apache.org. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ kamelets.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kameletbindings.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for flows Add a spec descriptor for kamelet Add a spec descriptor for profile Add a spec descriptor for resources Add a spec descriptor for build Add a spec descriptor for definition Add a spec descriptor for flow Add a spec descriptor for sink Add a spec descriptor for source For red-hat-camel-k-operator.v1.4.2: Owned CRDs do not have resources specified flows does not have a spec descriptor definition does not have a spec descriptor flow does not have a spec descriptor sink does not have a spec descriptor source does not have a spec descriptor error spec does not exist for the custom resource camel-k Add a spec descriptor for flows Add a spec descriptor for definition Add a spec descriptor for flow Add a spec descriptor for sink Add a spec descriptor for source builds.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status camelcatalogs.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrations.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationkits.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationplatforms.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kamelets.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kameletbindings.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [camel-k] For red-hat-camel-k-operator.v1.6.10: flows does not have a spec descriptor resources does not have a spec descriptor build does not have a spec descriptor kamelet does not have a spec descriptor profile does not have a spec descriptor definition does not have a spec descriptor flow does not have a spec descriptor sink does not have a spec descriptor source does not have a spec descriptor Owned CRDs do not have resources specified integrationplatforms.camel.apache.org does not have a status descriptor Add a spec descriptor for flows Add a spec descriptor for resources Add a spec descriptor for build Add a spec descriptor for kamelet Add a spec descriptor for profile Add a spec descriptor for definition Add a spec descriptor for flow Add a spec descriptor for sink Add a spec descriptor for source builds.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status camelcatalogs.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrations.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationkits.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd integrationplatforms.camel.apache.org. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ kamelets.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kameletbindings.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For red-hat-camel-k-operator.v1.6.10: flows does not have a spec descriptor resources does not have a spec descriptor build does not have a spec descriptor kamelet does not have a spec descriptor profile does not have a spec descriptor definition does not have a spec descriptor flow does not have a spec descriptor sink does not have a spec descriptor source does not have a spec descriptor Owned CRDs do not have resources specified integrationplatforms.camel.apache.org does not have a status descriptor Add a spec descriptor for flows Add a spec descriptor for resources Add a spec descriptor for build Add a spec descriptor for kamelet Add a spec descriptor for profile Add a spec descriptor for definition Add a spec descriptor for flow Add a spec descriptor for sink Add a spec descriptor for source builds.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status camelcatalogs.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrations.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status integrationkits.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd integrationplatforms.camel.apache.org. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ kamelets.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kameletbindings.camel.apache.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For red-hat-camel-k-operator.v1.8.0: Warning: Value red-hat-camel-k-operator.v1.8.0: unable to find the resource requests for the container: (camel-k-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value red-hat-camel-k-operator.v1.8.0: channel(s) ["latest" "1.8.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For red-hat-camel-k-operator.v1.8.0: Warning: Value red-hat-camel-k-operator.v1.8.0: unable to find the resource requests for the container: (camel-k-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value red-hat-camel-k-operator.v1.8.0: channel(s) ["latest" "1.8.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For red-hat-camel-k-operator.v1.8.0: Warning: Value red-hat-camel-k-operator.v1.8.0: unable to find the resource requests for the container: (camel-k-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value red-hat-camel-k-operator.v1.8.0: channel(s) ["latest" "1.8.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For red-hat-camel-k-operator.v1.4.2: Warning: Value red-hat-camel-k-operator.v1.4.2: unable to find the resource requests for the container: (camel-k-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value red-hat-camel-k-operator.v1.4.2: channel(s) ["1.4.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For red-hat-camel-k-operator.v1.6.10: Warning: Value red-hat-camel-k-operator.v1.6.10: unable to find the resource requests for the container: (camel-k-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value red-hat-camel-k-operator.v1.6.10: channel(s) ["1.6.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For red-hat-camel-k-operator.v1.6.10: Warning: Value red-hat-camel-k-operator.v1.6.10: unable to find the resource requests for the container: (camel-k-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value red-hat-camel-k-operator.v1.6.10: channel(s) ["1.6.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Full Lifecycle]	"Red Hat Integration" "Red Hat Application Foundations" "Red Hat Camel K"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
ocs-operator	PROBABLY COMPLY Following those complies: stable-4.11 stable-4.10	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. ocs-operator.v4.11.1 ocs-operator.v4.10.5	FIX ERRORS AND WARNINGS (+) For ocs-operator.v4.11.1: Owned CRDs do not have resources specified manageNodes does not have a spec descriptor monPVCTemplate does not have a spec descriptor storageDeviceSets does not have a spec descriptor storageclusters.ocs.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value ocs.openshift.io/v1, Kind=OCSInitialization: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBlockPool: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystem: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephRBDMirror: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZoneGroup: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplication: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucketClaim: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephCluster: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStoreUser: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZone: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketTopic: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBlockPoolRadosNamespace: provided API should have an example annotation Warning: Value ocs.openshift.io/v1alpha1, Kind=StorageClassClaim: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemMirror: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucket: provided API should have an example annotation Warning: Value ocs.openshift.io/v1alpha1, Kind=StorageConsumer: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStore: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephNFS: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephClient: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectRealm: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketNotification: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemSubVolumeGroup: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplicationClass: provided API should have an example annotation Add a spec descriptor for manageNodes Add a spec descriptor for monPVCTemplate Add a spec descriptor for storageDeviceSets For ocs-operator.v4.10.5: Owned CRDs do not have resources specified manageNodes does not have a spec descriptor monPVCTemplate does not have a spec descriptor storageDeviceSets does not have a spec descriptor storageclusters.ocs.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for manageNodes Add a spec descriptor for monPVCTemplate Add a spec descriptor for storageDeviceSets Warning: Value ceph.rook.io/v1, Kind=CephFilesystemSubVolumeGroup: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplicationClass: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplication: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephCluster: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystem: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectRealm: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZone: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucketClaim: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketTopic: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBlockPool: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStoreUser: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephClient: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephRBDMirror: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZoneGroup: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketNotification: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucket: provided API should have an example annotation Warning: Value ocs.openshift.io/v1, Kind=OCSInitialization: provided API should have an example annotation Warning: Value ocs.openshift.io/v1alpha1, Kind=StorageConsumer: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStore: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephNFS: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemMirror: provided API should have an example annotation	CHECK THE WARNINGS (+) For ocs-operator.v4.11.1: Warning: Value ocs-operator.v4.11.1: unable to find the resource requests for the container: (ocs-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value ocs-operator.v4.11.1: unable to find the resource requests for the container: (rook-ceph-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value ocs-operator.v4.11.1: unable to find the resource requests for the container: (ocs-metrics-exporter). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value ocs-operator.v4.11.1: owned CRD "volumereplicationclasses.replication.storage.openshift.io" has an empty description Warning: Value ocs-operator.v4.11.1: owned CRD "volumereplications.replication.storage.openshift.io" has an empty description Warning: Value ocs-operator.v4.11.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value ceph.rook.io/v1, Kind=CephObjectStore: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStoreUser: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephNFS: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZoneGroup: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucketClaim: provided API should have an example annotation Warning: Value ocs.openshift.io/v1, Kind=OCSInitialization: provided API should have an example annotation Warning: Value ocs.openshift.io/v1alpha1, Kind=StorageConsumer: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephClient: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystem: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemMirror: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephRBDMirror: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketNotification: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucket: provided API should have an example annotation Warning: Value ocs.openshift.io/v1alpha1, Kind=StorageClassClaim: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBlockPool: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketTopic: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemSubVolumeGroup: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBlockPoolRadosNamespace: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplicationClass: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplication: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephCluster: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectRealm: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZone: provided API should have an example annotation For ocs-operator.v4.10.5: Warning: Value ocs-operator.v4.10.5: unable to find the resource requests for the container: (ocs-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value ocs-operator.v4.10.5: unable to find the resource requests for the container: (rook-ceph-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value ocs-operator.v4.10.5: unable to find the resource requests for the container: (ocs-metrics-exporter). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value ocs-operator.v4.10.5: owned CRD "volumereplicationclasses.replication.storage.openshift.io" has an empty description Warning: Value ocs-operator.v4.10.5: owned CRD "volumereplications.replication.storage.openshift.io" has an empty description Warning: Value ocs-operator.v4.10.5: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value ceph.rook.io/v1, Kind=CephObjectZoneGroup: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketTopic: provided API should have an example annotation Warning: Value ocs.openshift.io/v1, Kind=OCSInitialization: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBlockPool: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephNFS: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephClient: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemMirror: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectRealm: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplicationClass: provided API should have an example annotation Warning: Value replication.storage.openshift.io/v1alpha1, Kind=VolumeReplication: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucket: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStore: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectStoreUser: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephBucketNotification: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystemSubVolumeGroup: provided API should have an example annotation Warning: Value ocs.openshift.io/v1alpha1, Kind=StorageConsumer: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephCluster: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephFilesystem: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephRBDMirror: provided API should have an example annotation Warning: Value ceph.rook.io/v1, Kind=CephObjectZone: provided API should have an example annotation Warning: Value objectbucket.io/v1alpha1, Kind=ObjectBucketClaim: provided API should have an example annotation	[Deep Insights]	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
openshift-pipelines-operator-rh	NOT COMPLY Following those does NOT complies: (+) . pipelines-1.7 pipelines-1.8 latest	USED	FIX ERRORS AND WARNINGS (+) For openshift-pipelines-operator-rh.v1.7.2: Owned CRDs do not have resources specified targetNamespace does not have a spec descriptor params does not have a spec descriptor pruner does not have a spec descriptor addon does not have a spec descriptor api does not have a spec descriptor Add a spec descriptor for targetNamespace Add a spec descriptor for params Add a spec descriptor for pruner Add a spec descriptor for addon Add a spec descriptor for api tektonaddons.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonchains.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonconfigs.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonhubs.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektoninstallersets.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonpipelines.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektontriggers.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add CRD validation for spec field `targetNamespace` in TektonAddon/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonChain/v1alpha1 Add CRD validation for spec field `addon` in TektonConfig/v1alpha1 Add CRD validation for spec field `params` in TektonConfig/v1alpha1 Add CRD validation for spec field `profile` in TektonConfig/v1alpha1 Add CRD validation for spec field `pruner` in TektonConfig/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonConfig/v1alpha1 Add CRD validation for spec field `api` in TektonHub/v1alpha1 Add CRD validation for spec field `manifests` in TektonInstallerSet/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonPipeline/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonTrigger/v1alpha1 For openshift-pipelines-operator-rh.v1.8.0: targetNamespace does not have a spec descriptor params does not have a spec descriptor pruner does not have a spec descriptor addon does not have a spec descriptor api does not have a spec descriptor Owned CRDs do not have resources specified Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead Add CRD validation for spec field `targetNamespace` in TektonAddon/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonChain/v1alpha1 Add CRD validation for spec field `addon` in TektonConfig/v1alpha1 Add CRD validation for spec field `params` in TektonConfig/v1alpha1 Add CRD validation for spec field `profile` in TektonConfig/v1alpha1 Add CRD validation for spec field `pruner` in TektonConfig/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonConfig/v1alpha1 Add CRD validation for spec field `api` in TektonHub/v1alpha1 Add CRD validation for spec field `manifests` in TektonInstallerSet/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonPipeline/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonTrigger/v1alpha1 tektonaddons.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonchains.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonconfigs.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonhubs.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektoninstallersets.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonpipelines.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektontriggers.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for targetNamespace Add a spec descriptor for params Add a spec descriptor for pruner Add a spec descriptor for addon Add a spec descriptor for api For openshift-pipelines-operator-rh.v1.8.0: targetNamespace does not have a spec descriptor params does not have a spec descriptor pruner does not have a spec descriptor addon does not have a spec descriptor api does not have a spec descriptor Owned CRDs do not have resources specified Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead Add CRD validation for spec field `targetNamespace` in TektonAddon/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonChain/v1alpha1 Add CRD validation for spec field `addon` in TektonConfig/v1alpha1 Add CRD validation for spec field `params` in TektonConfig/v1alpha1 Add CRD validation for spec field `profile` in TektonConfig/v1alpha1 Add CRD validation for spec field `pruner` in TektonConfig/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonConfig/v1alpha1 Add CRD validation for spec field `api` in TektonHub/v1alpha1 Add CRD validation for spec field `manifests` in TektonInstallerSet/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonPipeline/v1alpha1 Add CRD validation for spec field `targetNamespace` in TektonTrigger/v1alpha1 tektonaddons.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonchains.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonconfigs.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonhubs.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektoninstallersets.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektonpipelines.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektontriggers.operator.tekton.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for targetNamespace Add a spec descriptor for params Add a spec descriptor for pruner Add a spec descriptor for addon Add a spec descriptor for api	CHECK THE WARNINGS (+) For openshift-pipelines-operator-rh.v1.7.2: Warning: Value openshift-pipelines-operator-rh.v1.7.2: unable to find the resource requests for the container: (openshift-pipelines-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.7.2: unable to find the resource requests for the container: (tekton-operator-webhook). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.7.2: owned CRD "tektonchains.operator.tekton.dev" has an empty description Warning: Value openshift-pipelines-operator-rh.v1.7.2: owned CRD "tektonhubs.operator.tekton.dev" has an empty description Warning: Value openshift-pipelines-operator-rh.v1.7.2: channel(s) ["latest" "pipelines-1.7"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value openshift-pipelines-operator-rh.v1.7.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (openshift-pipelines-operator-rh.v1.7.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-pipelines-operator-rh.v1.8.0: Warning: Value openshift-pipelines-operator-rh.v1.8.0: unable to find the resource requests for the container: (openshift-pipelines-operator-lifecycle). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.8.0: unable to find the resource requests for the container: (openshift-pipelines-operator-cluster-operations). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.8.0: unable to find the resource requests for the container: (tekton-operator-webhook). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.8.0: owned CRD "tektonchains.operator.tekton.dev" has an empty description Warning: Value openshift-pipelines-operator-rh.v1.8.0: channel(s) ["latest" "pipelines-1.8"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value openshift-pipelines-operator-rh.v1.8.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (openshift-pipelines-operator-rh.v1.8.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead For openshift-pipelines-operator-rh.v1.8.0: Warning: Value openshift-pipelines-operator-rh.v1.8.0: unable to find the resource requests for the container: (openshift-pipelines-operator-lifecycle). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.8.0: unable to find the resource requests for the container: (openshift-pipelines-operator-cluster-operations). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.8.0: unable to find the resource requests for the container: (tekton-operator-webhook). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-pipelines-operator-rh.v1.8.0: owned CRD "tektonchains.operator.tekton.dev" has an empty description Warning: Value openshift-pipelines-operator-rh.v1.8.0: channel(s) ["latest" "pipelines-1.8"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value openshift-pipelines-operator-rh.v1.8.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (openshift-pipelines-operator-rh.v1.8.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead	[Full Lifecycle]	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (apiGroups/resources): autoscaling/horizontalpodautoscalers (apiGroups/resources): policy/podsecuritypolicies (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
opentelemetry-product	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For opentelemetry-operator.v0.56.0-1: exporter does not have a spec descriptor config does not have a spec descriptor instrumentations.opentelemetry.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status opentelemetrycollectors.opentelemetry.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for exporter Add a spec descriptor for config	CHECK THE WARNINGS (+) For opentelemetry-operator.v0.56.0-1: Warning: Value : (opentelemetry-operator.v0.56.0-1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): autoscaling/horizontalpodautoscalers (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
windows-machine-config-operator	NOT COMPLY Following those does NOT complies: (+) . preview Following those complies: stable	SHOULD SUPPORT	PASSED IN ALL CHECKS	CHECK THE WARNINGS (+) For windows-machine-config-operator.v6.0.0: Warning: Value windows-machine-config-operator.v6.0.0: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value windows-machine-config-operator.v6.0.0: channel(s) ["preview"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For windows-machine-config-operator.v6.0.0: Warning: Value windows-machine-config-operator.v6.0.0: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value windows-machine-config-operator.v6.0.0: channel(s) ["preview"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"Red Hat OpenShift support for Windows Containers"		USED	NOT USED
bamoe-businessautomation-operator	NOT COMPLY Following those does NOT complies: (+) . 8.x-stable	USED	CHECK THE WARNINGS (+) For bamoe-businessautomation-operator.8.0.0-1: kieapps.app.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For bamoe-businessautomation-operator.8.0.0-1: Warning: Value bamoe-businessautomation-operator.8.0.0-1: unable to find the resource requests for the container: (bamoe-business-automation-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value bamoe-businessautomation-operator.8.0.0-1: channel(s) ["8.x-stable"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value bamoe-businessautomation-operator.8.0.0-1: csv.metadata.Name bamoe-businessautomation-operator.8.0.0-1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (bamoe-businessautomation-operator.8.0.0-1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		NOT USED	NOT USED
cincinnati-operator	NOT COMPLY Following those does NOT complies: (+) . v1	SHOULD SUPPORT	CHECK THE WARNINGS (+) For update-service-operator.v5.0.0: updateservices.updateservice.operator.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For update-service-operator.v5.0.0: Warning: Value update-service-operator.v5.0.0: unable to find the resource requests for the container: (updateservice-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value update-service-operator.v5.0.0: channel(s) ["v1"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (update-service-operator.v5.0.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
nfd	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For nfd.4.11.0-202208291725: Owned CRDs do not have resources specified customConfig does not have a spec descriptor operand does not have a spec descriptor workerConfig does not have a spec descriptor rules does not have a spec descriptor Warning: Value topology.node.k8s.io/v1alpha1, Kind=NodeResourceTopology: provided API should have an example annotation nodefeaturediscoveries.nfd.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status nodefeaturerules.nfd.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for customConfig Add a spec descriptor for operand Add a spec descriptor for workerConfig Add a spec descriptor for rules	CHECK THE WARNINGS (+) For nfd.4.11.0-202208291725: Warning: Value nfd.4.11.0-202208291725: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value nfd.4.11.0-202208291725: csv.metadata.Name nfd.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value topology.node.k8s.io/v1alpha1, Kind=NodeResourceTopology: provided API should have an example annotation	[Deep Insights]	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/podsecuritypolicies (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
servicemeshoperator	NOT COMPLY Following those does NOT complies: (+) . 1.0 Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For servicemeshoperator.v2.2.2: tracing does not have a spec descriptor policy does not have a spec descriptor telemetry does not have a spec descriptor addons does not have a spec descriptor members does not have a spec descriptor controlPlaneRef does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for tracing Add a spec descriptor for policy Add a spec descriptor for telemetry Add a spec descriptor for addons Add a spec descriptor for members Add a spec descriptor for controlPlaneRef servicemeshcontrolplanes.maistra.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicemeshmemberrolls.maistra.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicemeshmembers.maistra.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For servicemeshoperator.v2.2.2: tracing does not have a spec descriptor policy does not have a spec descriptor telemetry does not have a spec descriptor addons does not have a spec descriptor members does not have a spec descriptor controlPlaneRef does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for tracing Add a spec descriptor for policy Add a spec descriptor for telemetry Add a spec descriptor for addons Add a spec descriptor for members Add a spec descriptor for controlPlaneRef servicemeshcontrolplanes.maistra.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicemeshmemberrolls.maistra.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicemeshmembers.maistra.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For servicemeshoperator.v2.2.2: Warning: Value servicemeshoperator.v2.2.2: unable to find the resource requests for the container: (istio-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value servicemeshoperator.v2.2.2: channel(s) ["1.0"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value servicemeshoperator.v2.2.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (servicemeshoperator.v2.2.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For servicemeshoperator.v2.2.2: Warning: Value servicemeshoperator.v2.2.2: unable to find the resource requests for the container: (istio-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value servicemeshoperator.v2.2.2: channel(s) ["1.0"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value servicemeshoperator.v2.2.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (servicemeshoperator.v2.2.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): autoscaling/horizontalpodautoscalers (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
vertical-pod-autoscaler	PROBABLY COMPLY Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For verticalpodautoscaler.4.11.0-202208291725: Owned CRDs do not have resources specified podMinCPUMillicores does not have a spec descriptor podMinMemoryMb does not have a spec descriptor recommendationOnly does not have a spec descriptor safetyMarginFraction does not have a spec descriptor minReplicas does not have a spec descriptor targetRef does not have a spec descriptor resourcePolicy does not have a spec descriptor Warning: Value autoscaling.k8s.io/v1, Kind=VerticalPodAutoscalerCheckpoint: provided API should have an example annotation Add a spec descriptor for podMinCPUMillicores Add a spec descriptor for podMinMemoryMb Add a spec descriptor for recommendationOnly Add a spec descriptor for safetyMarginFraction Add a spec descriptor for minReplicas Add a spec descriptor for targetRef Add a spec descriptor for resourcePolicy verticalpodautoscalercontrollers.autoscaling.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status verticalpodautoscalers.autoscaling.k8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For verticalpodautoscaler.4.11.0-202208291725: Warning: Value verticalpodautoscaler.4.11.0-202208291725: csv.metadata.Name verticalpodautoscaler.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value autoscaling.k8s.io/v1, Kind=VerticalPodAutoscalerCheckpoint: provided API should have an example annotation	[Full Lifecycle]	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
openshift-secondary-scheduler-operator	PROBABLY COMPLY Following those complies: stable	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. secondaryscheduleroperator.v1.1.0	FIX ERRORS AND WARNINGS (+) For secondaryscheduleroperator.v1.1.0: schedulerConfig does not have a spec descriptor managementState does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for schedulerConfig Add a spec descriptor for managementState secondaryschedulers.operator.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	PASSED IN ALL CHECKS	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		NOT USED	NOT USED
rh-service-binding-operator	NOT COMPLY Following those does NOT complies: (+) . preview beta Following those complies: candidate stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For service-binding-operator.v0.11.0: application does not have a spec descriptor services does not have a spec descriptor application does not have a spec descriptor service does not have a spec descriptor Owned CRDs do not have resources specified error spec does not exist for the custom resource bindablekinds-sample Add a spec descriptor for application Add a spec descriptor for services Add a spec descriptor for application Add a spec descriptor for service Add CRD validation for spec field `application` in ServiceBinding/v1alpha3 spec missing from [bindablekinds-sample] bindablekinds.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For service-binding-operator.v0.10.0: application does not have a spec descriptor services does not have a spec descriptor application does not have a spec descriptor service does not have a spec descriptor Owned CRDs do not have resources specified servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for application Add a spec descriptor for services Add a spec descriptor for application Add a spec descriptor for service For service-binding-operator.v0.9.1: Owned CRDs do not have resources specified Error: Value service-binding-operator: invalid service account found in bundle. This service account service-binding-operator in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. application does not have a spec descriptor services does not have a spec descriptor application does not have a spec descriptor service does not have a spec descriptor servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for application Add a spec descriptor for services Add a spec descriptor for application Add a spec descriptor for service For service-binding-operator.v1.1.1: application does not have a spec descriptor services does not have a spec descriptor application does not have a spec descriptor service does not have a spec descriptor Owned CRDs do not have resources specified Warning: Value binding.operators.coreos.com/v1alpha1, Kind=BindableKinds: provided API should have an example annotation Warning: Value servicebinding.io/v1alpha3, Kind=ClusterWorkloadResourceMapping: provided API should have an example annotation Add a spec descriptor for application Add a spec descriptor for services Add a spec descriptor for application Add a spec descriptor for service servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status servicebindings.binding.operators.coreos.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add CRD validation for spec field `application` in ServiceBinding/v1alpha3	FIX ERRORS AND WARNINGS (+) For service-binding-operator.v0.11.0: Warning: Value service-binding-operator.v0.11.0: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ For service-binding-operator.v0.10.0: Warning: Value service-binding-operator.v0.10.0: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value service-binding-operator.v0.10.0: channel(s) ["preview"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For service-binding-operator.v0.9.1: Error: Value service-binding-operator: invalid service account found in bundle. This service account service-binding-operator in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Warning: Value service-binding-operator.v0.9.1: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value service-binding-operator.v0.9.1: channel(s) ["beta" "preview"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (service-binding-operator.v0.9.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For service-binding-operator.v1.1.1: Warning: Value service-binding-operator.v1.1.1: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value service-binding-operator.v1.1.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value binding.operators.coreos.com/v1alpha1, Kind=BindableKinds: provided API should have an example annotation Warning: Value servicebinding.io/v1alpha3, Kind=ClusterWorkloadResourceMapping: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
rhsso-operator	NOT COMPLY Following those does NOT complies: (+) . alpha Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For rhsso-operator.7.6.0-opr-003: instances does not have a spec descriptor externalAccess does not have a spec descriptor realm does not have a spec descriptor instanceSelector does not have a spec descriptor instanceSelector does not have a spec descriptor client does not have a spec descriptor realmSelector does not have a spec descriptor realmSelector does not have a spec descriptor user does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for instances Add a spec descriptor for externalAccess Add a spec descriptor for realm Add a spec descriptor for instanceSelector Add a spec descriptor for instanceSelector Add a spec descriptor for client Add a spec descriptor for realmSelector Add a spec descriptor for realmSelector Add a spec descriptor for user keycloaks.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakrealms.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakbackups.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakclients.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakusers.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhsso-operator.7.5.1-opr-005: Owned CRDs do not have resources specified instances does not have a spec descriptor externalAccess does not have a spec descriptor realm does not have a spec descriptor instanceSelector does not have a spec descriptor instanceSelector does not have a spec descriptor realmSelector does not have a spec descriptor client does not have a spec descriptor user does not have a spec descriptor realmSelector does not have a spec descriptor keycloaks.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakrealms.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakbackups.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakclients.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status keycloakusers.keycloak.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for instances Add a spec descriptor for externalAccess Add a spec descriptor for realm Add a spec descriptor for instanceSelector Add a spec descriptor for instanceSelector Add a spec descriptor for realmSelector Add a spec descriptor for client Add a spec descriptor for user Add a spec descriptor for realmSelector	CHECK THE WARNINGS (+) For rhsso-operator.7.6.0-opr-003: Warning: Value rhsso-operator.7.6.0-opr-003: unable to find the resource requests for the container: (rhsso-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhsso-operator.7.6.0-opr-003: csv.metadata.Name rhsso-operator.7.6.0-opr-003 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (rhsso-operator.7.6.0-opr-003) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For rhsso-operator.7.5.1-opr-005: Warning: Value rhsso-operator.7.5.1-opr-005: unable to find the resource requests for the container: (rhsso-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhsso-operator.7.5.1-opr-005: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value rhsso-operator.7.5.1-opr-005: csv.metadata.Name rhsso-operator.7.5.1-opr-005 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (rhsso-operator.7.5.1-opr-005) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Full Lifecycle]	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
fuse-apicurito	NOT COMPLY Following those does NOT complies: (+) . fuse-apicurito-7.11.x fuse-apicurito-7.10.x fuse-apicurito-7.9.x	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For fuse-apicurito.v7.11.0-0.1662457152.p: size does not have a spec descriptor Add a spec descriptor for size apicuritoes.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-apicurito.v7.9.3: Owned CRDs do not have resources specified apicuritoes.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-apicurito.v7.10.3: size does not have a spec descriptor apicuritoes.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for size	CHECK THE WARNINGS (+) For fuse-apicurito.v7.11.0-0.1662457152.p: Warning: Value fuse-apicurito.v7.11.0-0.1662457152.p: unable to find the resource requests for the container: (fuse-apicurito). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-apicurito.v7.11.0-0.1662457152.p: channel(s) ["fuse-apicurito-7.11.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-apicurito.v7.11.0-0.1662457152.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-apicurito.v7.9.3: Warning: Value fuse-apicurito.v7.9.3: unable to find the resource requests for the container: (fuse-apicurito). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-apicurito.v7.9.3: channel(s) ["fuse-apicurito-7.9.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-apicurito.v7.9.3) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-apicurito.v7.10.3: Warning: Value fuse-apicurito.v7.10.3: unable to find the resource requests for the container: (fuse-apicurito). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-apicurito.v7.10.3: channel(s) ["fuse-apicurito-7.10.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-apicurito.v7.10.3) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
jws-operator	NOT COMPLY Following those does NOT complies: (+) . alpha	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For jws-operator.v2.0.1: Owned CRDs do not have resources specified applicationName does not have a spec descriptor replicas does not have a spec descriptor webImage does not have a spec descriptor applicationName does not have a spec descriptor replicas does not have a spec descriptor webImageStream does not have a spec descriptor webservers.web.servers.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status webservers.web.servers.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for applicationName Add a spec descriptor for replicas Add a spec descriptor for webImage Add a spec descriptor for applicationName Add a spec descriptor for replicas Add a spec descriptor for webImageStream	CHECK THE WARNINGS (+) For jws-operator.v2.0.1: Warning: Value jws-operator.v2.0.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value jws-operator.v2.0.1: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (jws-operator.v2.0.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
klusterlet-product	NOT COMPLY Following those does NOT complies: (+) . backplane-2.0 Following those complies: stable-2.1	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For klusterlet-product.v2.0.2: Owned CRDs do not have resources specified namespace does not have a spec descriptor registrationImagePullSpec does not have a spec descriptor workImagePullSpec does not have a spec descriptor clusterName does not have a spec descriptor externalServerURLs does not have a spec descriptor klusterlets.operator.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for namespace Add a spec descriptor for registrationImagePullSpec Add a spec descriptor for workImagePullSpec Add a spec descriptor for clusterName Add a spec descriptor for externalServerURLs For klusterlet-product.v2.1.1: Owned CRDs do not have resources specified registrationImagePullSpec does not have a spec descriptor workImagePullSpec does not have a spec descriptor clusterName does not have a spec descriptor externalServerURLs does not have a spec descriptor namespace does not have a spec descriptor Add a spec descriptor for registrationImagePullSpec Add a spec descriptor for workImagePullSpec Add a spec descriptor for clusterName Add a spec descriptor for externalServerURLs Add a spec descriptor for namespace klusterlets.operator.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For klusterlet-product.v2.0.2: Warning: Value klusterlet-product.v2.0.2: channel(s) ["backplane-2.0"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value klusterlet-product.v2.0.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (klusterlet-product.v2.0.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For klusterlet-product.v2.1.1: Warning: Value klusterlet-product.v2.1.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (klusterlet-product.v2.1.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"Openshift Kubernetes Engine" "Openshift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
loki-operator	PROBABLY COMPLY Following those complies: candidate stable stable-5.5	SHOULD SUPPORT	CHECK THE WARNINGS (+) For loki-operator.5.4.5: alertingrules.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status lokistacks.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status recordingrules.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status rulerconfigs.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For loki-operator.5.5.1: lokistacks.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status alertingrules.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status recordingrules.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status rulerconfigs.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For loki-operator.5.5.1: lokistacks.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status alertingrules.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status recordingrules.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status rulerconfigs.loki.grafana.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For loki-operator.5.4.5: Warning: Value loki-operator.5.4.5: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value loki-operator.5.4.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value loki-operator.5.4.5: csv.metadata.Name loki-operator.5.4.5 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For loki-operator.5.5.1: Warning: Value loki-operator.5.5.1: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value loki-operator.5.5.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value loki-operator.5.5.1: csv.metadata.Name loki-operator.5.5.1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For loki-operator.5.5.1: Warning: Value loki-operator.5.5.1: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value loki-operator.5.5.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value loki-operator.5.5.1: csv.metadata.Name loki-operator.5.5.1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1	[Full Lifecycle]	NOT ADDED		USED	NOT USED
mtc-operator	NOT COMPLY Following those does NOT complies: (+) . release-v1.7	USED	FIX ERRORS AND WARNINGS (+) For mtc-operator.v1.7.4: Owned CRDs do not have resources specified azure_resource_group does not have a spec descriptor migration_velero does not have a spec descriptor migration_ui does not have a spec descriptor restic_timeout does not have a spec descriptor mig_namespace_limit does not have a spec descriptor cluster_name does not have a spec descriptor migration_controller does not have a spec descriptor migration_log_reader does not have a spec descriptor olm_managed does not have a spec descriptor mig_pv_limit does not have a spec descriptor mig_pod_limit does not have a spec descriptor plan does not have a spec descriptor analyzeK8SResources does not have a spec descriptor analyzeImageCount does not have a spec descriptor analyzePVCapacity does not have a spec descriptor Warning: Value migration.openshift.io/v1alpha1, Kind=MigHook: provided API should have an example annotation Add a spec descriptor for azure_resource_group Add a spec descriptor for migration_velero Add a spec descriptor for migration_ui Add a spec descriptor for restic_timeout Add a spec descriptor for mig_namespace_limit Add a spec descriptor for cluster_name Add a spec descriptor for migration_controller Add a spec descriptor for migration_log_reader Add a spec descriptor for olm_managed Add a spec descriptor for mig_pv_limit Add a spec descriptor for mig_pod_limit Add a spec descriptor for plan Add a spec descriptor for analyzeK8SResources Add a spec descriptor for analyzeImageCount Add a spec descriptor for analyzePVCapacity migrationcontrollers.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status directimagemigrations.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status directimagestreammigrations.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status miganalytics.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migclusters.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status directvolumemigrations.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status directvolumemigrationprogresses.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migplans.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migmigrations.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migstorages.migration.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add CRD validation for spec field `azure_resource_group` in MigrationController/v1alpha1 Add CRD validation for spec field `migration_velero` in MigrationController/v1alpha1 Add CRD validation for spec field `migration_controller` in MigrationController/v1alpha1 Add CRD validation for spec field `migration_ui` in MigrationController/v1alpha1 Add CRD validation for spec field `mig_pv_limit` in MigrationController/v1alpha1 Add CRD validation for spec field `mig_pod_limit` in MigrationController/v1alpha1 Add CRD validation for spec field `mig_namespace_limit` in MigrationController/v1alpha1 Add CRD validation for spec field `cluster_name` in MigrationController/v1alpha1 Add CRD validation for spec field `migration_log_reader` in MigrationController/v1alpha1 Add CRD validation for spec field `olm_managed` in MigrationController/v1alpha1 Add CRD validation for spec field `restic_timeout` in MigrationController/v1alpha1 Add CRD validation for spec field `plan` in MigAnalytic/v1alpha1	CHECK THE WARNINGS (+) For mtc-operator.v1.7.4: Warning: Value mtc-operator.v1.7.4: unable to find the resource requests for the container: (operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mtc-operator.v1.7.4: channel(s) ["release-v1.7"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value mtc-operator.v1.7.4: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (mtc-operator.v1.7.4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value migration.openshift.io/v1alpha1, Kind=MigHook: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (All from apiGroups): batch/* (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
service-registry-operator	NOT COMPLY Following those does NOT complies: (+) . 2.0.x 2.x	USED	FIX ERRORS AND WARNINGS (+) For service-registry-operator.v2.0.7-0.1661784420.p: configuration does not have a spec descriptor configuration does not have a spec descriptor Owned CRDs do not have resources specified apicurioregistries.registry.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apicurioregistries.registry.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for configuration Add a spec descriptor for configuration For service-registry-operator.v2.0.7-0.1661784420.p: configuration does not have a spec descriptor configuration does not have a spec descriptor Owned CRDs do not have resources specified apicurioregistries.registry.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apicurioregistries.registry.apicur.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for configuration Add a spec descriptor for configuration	CHECK THE WARNINGS (+) For service-registry-operator.v2.0.7-0.1661784420.p: Warning: Value service-registry-operator.v2.0.7-0.1661784420.p: channel(s) ["2.0.x" "2.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (service-registry-operator.v2.0.7-0.1661784420.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For service-registry-operator.v2.0.7-0.1661784420.p: Warning: Value service-registry-operator.v2.0.7-0.1661784420.p: channel(s) ["2.0.x" "2.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (service-registry-operator.v2.0.7-0.1661784420.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
web-terminal	PROBABLY COMPLY Following those complies: fast	SHOULD SUPPORT	PASSED IN ALL CHECKS	CHECK THE WARNINGS (+) For web-terminal.v1.5.1-0.1661829403.p: Warning: Value web-terminal.v1.5.1-0.1661829403.p: unable to find the resource requests for the container: (web-terminal-controller). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value web-terminal.v1.5.1-0.1661829403.p: required CRD "devworkspaceroutings.controller.devfile.io" has an empty description Warning: Value web-terminal.v1.5.1-0.1661829403.p: required CRD "devworkspaces.workspace.devfile.io" has an empty description Warning: Value : (web-terminal.v1.5.1-0.1661829403.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		NOT USED	NOT USED
amq7-interconnect-operator	NOT COMPLY Following those does NOT complies: (+) . 1.2.0 1.10.x latest	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For amq7-interconnect-operator.v1.10.9: deploymentPlan does not have a spec descriptor interconnects.interconnectedcloud.github.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for deploymentPlan For amq7-interconnect-operator.v1.10.9: deploymentPlan does not have a spec descriptor interconnects.interconnectedcloud.github.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for deploymentPlan For amq7-interconnect-operator.v1.10.9: deploymentPlan does not have a spec descriptor interconnects.interconnectedcloud.github.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for deploymentPlan	CHECK THE WARNINGS (+) For amq7-interconnect-operator.v1.10.9: Warning: Value amq7-interconnect-operator.v1.10.9: unable to find the resource requests for the container: (interconnect-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amq7-interconnect-operator.v1.10.9: channel(s) ["1.2.0" "1.10.x" "latest"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (amq7-interconnect-operator.v1.10.9) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For amq7-interconnect-operator.v1.10.9: Warning: Value amq7-interconnect-operator.v1.10.9: unable to find the resource requests for the container: (interconnect-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amq7-interconnect-operator.v1.10.9: channel(s) ["1.2.0" "1.10.x" "latest"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (amq7-interconnect-operator.v1.10.9) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For amq7-interconnect-operator.v1.10.9: Warning: Value amq7-interconnect-operator.v1.10.9: unable to find the resource requests for the container: (interconnect-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amq7-interconnect-operator.v1.10.9: channel(s) ["1.2.0" "1.10.x" "latest"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (amq7-interconnect-operator.v1.10.9) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"Red Hat Integration" "Red Hat AMQ"		NOT USED	NOT USED
aws-efs-csi-driver-operator	PROBABLY COMPLY Following those complies: stable	SHOULD SUPPORT	CHECK THE WARNINGS (+) For aws-efs-csi-driver-operator.4.11.0-202208291725: Warning: Value : (aws-efs-csi-driver-operator.4.11.0-202208291725) example annotations not found	CHECK THE WARNINGS (+) For aws-efs-csi-driver-operator.4.11.0-202208291725: Warning: Value aws-efs-csi-driver-operator.4.11.0-202208291725: csv.metadata.Name aws-efs-csi-driver-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (aws-efs-csi-driver-operator.4.11.0-202208291725) example annotations not found	[Full Lifecycle]	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		NOT USED	NOT USED
aws-load-balancer-operator	NOT COMPLY Following those does NOT complies: (+) . alpha Following those complies: stable-v0.1	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For aws-load-balancer-operator.v0.0.1: serviceRef does not have a spec descriptor targetGroupARN does not have a spec descriptor group does not have a spec descriptor targetGroupARN does not have a spec descriptor serviceRef does not have a spec descriptor subnetTagging does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for serviceRef Add a spec descriptor for targetGroupARN Add a spec descriptor for group Add a spec descriptor for targetGroupARN Add a spec descriptor for serviceRef Add a spec descriptor for subnetTagging targetgroupbindings.elbv2.k8s.aws does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ingressclassparams.elbv2.k8s.aws does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status targetgroupbindings.elbv2.k8s.aws does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status awsloadbalancercontrollers.networking.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For aws-load-balancer-operator.v0.0.1: serviceRef does not have a spec descriptor targetGroupARN does not have a spec descriptor group does not have a spec descriptor targetGroupARN does not have a spec descriptor serviceRef does not have a spec descriptor subnetTagging does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for serviceRef Add a spec descriptor for targetGroupARN Add a spec descriptor for group Add a spec descriptor for targetGroupARN Add a spec descriptor for serviceRef Add a spec descriptor for subnetTagging targetgroupbindings.elbv2.k8s.aws does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ingressclassparams.elbv2.k8s.aws does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status targetgroupbindings.elbv2.k8s.aws does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status awsloadbalancercontrollers.networking.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For aws-load-balancer-operator.v0.0.1: Warning: Value aws-load-balancer-operator.v0.0.1: owned CRD "ingressclassparams.elbv2.k8s.aws" has an empty description Warning: Value aws-load-balancer-operator.v0.0.1: owned CRD "targetgroupbindings.elbv2.k8s.aws" has an empty description Warning: Value aws-load-balancer-operator.v0.0.1: owned CRD "targetgroupbindings.elbv2.k8s.aws" has an empty description Warning: Value aws-load-balancer-operator.v0.0.1: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For aws-load-balancer-operator.v0.0.1: Warning: Value aws-load-balancer-operator.v0.0.1: owned CRD "ingressclassparams.elbv2.k8s.aws" has an empty description Warning: Value aws-load-balancer-operator.v0.0.1: owned CRD "targetgroupbindings.elbv2.k8s.aws" has an empty description Warning: Value aws-load-balancer-operator.v0.0.1: owned CRD "targetgroupbindings.elbv2.k8s.aws" has an empty description Warning: Value aws-load-balancer-operator.v0.0.1: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
fuse-online	NOT COMPLY Following those does NOT complies: (+) . 7.11.x latest 7.10.x 7.9.x Following those complies: stable candidate	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. fuse-online.v7.11.0-0.1659517286.p fuse-online.v7.11.0-0.1659517286.p fuse-online.v7.10.4 fuse-online.v7.9.3 fuse-online.v7.11.0-0.1659517286.p fuse-online.v7.11.0-0.1659517286.p	FIX ERRORS AND WARNINGS (+) For fuse-online.v7.11.0-0.1659517286.p: syndesises.syndesis.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-online.v7.11.0-0.1659517286.p: syndesises.syndesis.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-online.v7.10.4: syndesises.syndesis.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-online.v7.9.3: addons does not have a spec descriptor Add a spec descriptor for addons syndesises.syndesis.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-online.v7.11.0-0.1659517286.p: syndesises.syndesis.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-online.v7.11.0-0.1659517286.p: syndesises.syndesis.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For fuse-online.v7.11.0-0.1659517286.p: Warning: Value fuse-online.v7.11.0-0.1659517286.p: unable to find the resource requests for the container: (syndesis-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-online.v7.11.0-0.1659517286.p: channel(s) ["latest" "7.11.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-online.v7.11.0-0.1659517286.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-online.v7.11.0-0.1659517286.p: Warning: Value fuse-online.v7.11.0-0.1659517286.p: unable to find the resource requests for the container: (syndesis-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-online.v7.11.0-0.1659517286.p: channel(s) ["latest" "7.11.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-online.v7.11.0-0.1659517286.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-online.v7.10.4: Warning: Value fuse-online.v7.10.4: unable to find the resource requests for the container: (syndesis-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-online.v7.10.4: channel(s) ["7.10.x" "latest"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-online.v7.10.4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-online.v7.9.3: Warning: Value fuse-online.v7.9.3: unable to find the resource requests for the container: (syndesis-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-online.v7.9.3: channel(s) ["7.9.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-online.v7.9.3) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-online.v7.11.0-0.1659517286.p: Warning: Value fuse-online.v7.11.0-0.1659517286.p: unable to find the resource requests for the container: (syndesis-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-online.v7.11.0-0.1659517286.p: channel(s) ["latest" "7.11.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-online.v7.11.0-0.1659517286.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-online.v7.11.0-0.1659517286.p: Warning: Value fuse-online.v7.11.0-0.1659517286.p: unable to find the resource requests for the container: (syndesis-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-online.v7.11.0-0.1659517286.p: channel(s) ["latest" "7.11.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-online.v7.11.0-0.1659517286.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
quay-bridge-operator	NOT COMPLY Following those does NOT complies: (+) . quay-v3.4 quay-v3.5 Following those complies: stable-3.7 stable-3.6	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. quay-bridge-operator.v3.4.7 quay-bridge-operator.v3.5.7	FIX ERRORS AND WARNINGS (+) For quay-bridge-operator.v3.7.8: Owned CRDs do not have resources specified quayintegrations.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For quay-bridge-operator.v3.4.7: Owned CRDs do not have resources specified clusterID does not have a spec descriptor credentialsSecretName does not have a spec descriptor quayHostname does not have a spec descriptor insecureRegistry does not have a spec descriptor quayintegrations.redhatcop.redhat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for clusterID Add a spec descriptor for credentialsSecretName Add a spec descriptor for quayHostname Add a spec descriptor for insecureRegistry For quay-bridge-operator.v3.6.10: Owned CRDs do not have resources specified quayintegrations.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For quay-bridge-operator.v3.5.7: Owned CRDs do not have resources specified clusterID does not have a spec descriptor credentialsSecretName does not have a spec descriptor quayHostname does not have a spec descriptor insecureRegistry does not have a spec descriptor quayintegrations.redhatcop.redhat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for clusterID Add a spec descriptor for credentialsSecretName Add a spec descriptor for quayHostname Add a spec descriptor for insecureRegistry	CHECK THE WARNINGS (+) For quay-bridge-operator.v3.7.8: Warning: Value quay-bridge-operator.v3.7.8: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (quay-bridge-operator.v3.7.8) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For quay-bridge-operator.v3.4.7: Warning: Value quay-bridge-operator.v3.4.7: unable to find the resource requests for the container: (quay-bridge-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value quay-bridge-operator.v3.4.7: channel(s) ["quay-v3.4"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (quay-bridge-operator.v3.4.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For quay-bridge-operator.v3.6.10: Warning: Value quay-bridge-operator.v3.6.10: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (quay-bridge-operator.v3.6.10) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For quay-bridge-operator.v3.5.7: Warning: Value quay-bridge-operator.v3.5.7: unable to find the resource requests for the container: (quay-bridge-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value quay-bridge-operator.v3.5.7: channel(s) ["quay-v3.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (quay-bridge-operator.v3.5.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Full Lifecycle]	"OpenShift Platform Plus" "Red Hat Quay"		USED	NOT USED
elasticsearch-operator	PROBABLY COMPLY Following those complies: stable-5.3 stable-5.4 stable stable-5.5 stable-5.2	USED	FIX ERRORS AND WARNINGS (+) For elasticsearch-operator.5.3.9: nodeSpec does not have a spec descriptor nodes does not have a spec descriptor redundancyPolicy does not have a spec descriptor indexManagement does not have a spec descriptor managementState does not have a spec descriptor managementState does not have a spec descriptor Add a spec descriptor for nodeSpec Add a spec descriptor for nodes Add a spec descriptor for redundancyPolicy Add a spec descriptor for indexManagement Add a spec descriptor for managementState Add a spec descriptor for managementState elasticsearches.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kibanas.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For elasticsearch-operator.5.4.5: indexManagement does not have a spec descriptor managementState does not have a spec descriptor nodeSpec does not have a spec descriptor nodes does not have a spec descriptor redundancyPolicy does not have a spec descriptor managementState does not have a spec descriptor elasticsearches.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kibanas.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for indexManagement Add a spec descriptor for managementState Add a spec descriptor for nodeSpec Add a spec descriptor for nodes Add a spec descriptor for redundancyPolicy Add a spec descriptor for managementState For elasticsearch-operator.5.5.1: nodeSpec does not have a spec descriptor nodes does not have a spec descriptor redundancyPolicy does not have a spec descriptor indexManagement does not have a spec descriptor managementState does not have a spec descriptor managementState does not have a spec descriptor Add a spec descriptor for nodeSpec Add a spec descriptor for nodes Add a spec descriptor for redundancyPolicy Add a spec descriptor for indexManagement Add a spec descriptor for managementState Add a spec descriptor for managementState elasticsearches.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kibanas.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For elasticsearch-operator.5.5.1: nodeSpec does not have a spec descriptor nodes does not have a spec descriptor redundancyPolicy does not have a spec descriptor indexManagement does not have a spec descriptor managementState does not have a spec descriptor managementState does not have a spec descriptor Add a spec descriptor for nodeSpec Add a spec descriptor for nodes Add a spec descriptor for redundancyPolicy Add a spec descriptor for indexManagement Add a spec descriptor for managementState Add a spec descriptor for managementState elasticsearches.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kibanas.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For elasticsearch-operator.5.2.12: managementState does not have a spec descriptor nodeSpec does not have a spec descriptor nodes does not have a spec descriptor redundancyPolicy does not have a spec descriptor indexManagement does not have a spec descriptor managementState does not have a spec descriptor Add a spec descriptor for managementState Add a spec descriptor for nodeSpec Add a spec descriptor for nodes Add a spec descriptor for redundancyPolicy Add a spec descriptor for indexManagement Add a spec descriptor for managementState elasticsearches.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kibanas.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For elasticsearch-operator.5.3.9: Warning: Value elasticsearch-operator.5.3.9: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.3.9: unable to find the resource requests for the container: (elasticsearch-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.3.9: csv.metadata.Name elasticsearch-operator.5.3.9 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For elasticsearch-operator.5.4.5: Warning: Value elasticsearch-operator.5.4.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.4.5: unable to find the resource requests for the container: (elasticsearch-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.4.5: csv.metadata.Name elasticsearch-operator.5.4.5 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For elasticsearch-operator.5.5.1: Warning: Value elasticsearch-operator.5.5.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.5.1: unable to find the resource requests for the container: (elasticsearch-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.5.1: csv.metadata.Name elasticsearch-operator.5.5.1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For elasticsearch-operator.5.5.1: Warning: Value elasticsearch-operator.5.5.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.5.1: unable to find the resource requests for the container: (elasticsearch-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.5.1: csv.metadata.Name elasticsearch-operator.5.5.1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For elasticsearch-operator.5.2.12: Warning: Value elasticsearch-operator.5.2.12: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.2.12: unable to find the resource requests for the container: (elasticsearch-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value elasticsearch-operator.5.2.12: csv.metadata.Name elasticsearch-operator.5.2.12 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1	[Full Lifecycle]	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
rhpam-kogito-operator	NOT COMPLY Following those does NOT complies: (+) . 7.x	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For rhpam-kogito-operator.v7.12.0-4: Owned CRDs do not have resources specified gitSource does not have a spec descriptor type does not have a spec descriptor resource does not have a spec descriptor replicas does not have a spec descriptor Add a spec descriptor for gitSource Add a spec descriptor for type Add a spec descriptor for resource Add a spec descriptor for replicas kogitobuilds.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kogitoinfras.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kogitoruntimes.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For rhpam-kogito-operator.v7.12.0-4: Warning: Value rhpam-kogito-operator.v7.12.0-4: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhpam-kogito-operator.v7.12.0-4: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhpam-kogito-operator.v7.12.0-4: channel(s) ["7.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (rhpam-kogito-operator.v7.12.0-4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
sriov-network-operator	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For sriov-network-operator.4.11.0-202208301406: Owned CRDs do not have resources specified linkState does not have a spec descriptor networkNamespace does not have a spec descriptor resourceName does not have a spec descriptor ipam does not have a spec descriptor vlan does not have a spec descriptor ipam does not have a spec descriptor networkNamespace does not have a spec descriptor resourceName does not have a spec descriptor spoofChk does not have a spec descriptor trust does not have a spec descriptor resourceName does not have a spec descriptor deviceType does not have a spec descriptor mtu does not have a spec descriptor nicSelector does not have a spec descriptor nodeSelector does not have a spec descriptor numVfs does not have a spec descriptor priority does not have a spec descriptor interfaces does not have a spec descriptor foo does not have a spec descriptor enableInjector does not have a spec descriptor enableOperatorWebhook does not have a spec descriptor logLevel does not have a spec descriptor Add CRD validation for spec field `foo` in SriovNetworkPoolConfig/v1 sriovibnetworks.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworks.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworknodepolicies.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworknodestates.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworkpoolconfigs.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovoperatorconfigs.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for linkState Add a spec descriptor for networkNamespace Add a spec descriptor for resourceName Add a spec descriptor for ipam Add a spec descriptor for vlan Add a spec descriptor for ipam Add a spec descriptor for networkNamespace Add a spec descriptor for resourceName Add a spec descriptor for spoofChk Add a spec descriptor for trust Add a spec descriptor for resourceName Add a spec descriptor for deviceType Add a spec descriptor for mtu Add a spec descriptor for nicSelector Add a spec descriptor for nodeSelector Add a spec descriptor for numVfs Add a spec descriptor for priority Add a spec descriptor for interfaces Add a spec descriptor for foo Add a spec descriptor for enableInjector Add a spec descriptor for enableOperatorWebhook Add a spec descriptor for logLevel For sriov-network-operator.4.11.0-202208301406: Owned CRDs do not have resources specified linkState does not have a spec descriptor networkNamespace does not have a spec descriptor resourceName does not have a spec descriptor ipam does not have a spec descriptor vlan does not have a spec descriptor ipam does not have a spec descriptor networkNamespace does not have a spec descriptor resourceName does not have a spec descriptor spoofChk does not have a spec descriptor trust does not have a spec descriptor resourceName does not have a spec descriptor deviceType does not have a spec descriptor mtu does not have a spec descriptor nicSelector does not have a spec descriptor nodeSelector does not have a spec descriptor numVfs does not have a spec descriptor priority does not have a spec descriptor interfaces does not have a spec descriptor foo does not have a spec descriptor enableInjector does not have a spec descriptor enableOperatorWebhook does not have a spec descriptor logLevel does not have a spec descriptor Add CRD validation for spec field `foo` in SriovNetworkPoolConfig/v1 sriovibnetworks.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworks.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworknodepolicies.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworknodestates.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovnetworkpoolconfigs.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status sriovoperatorconfigs.sriovnetwork.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for linkState Add a spec descriptor for networkNamespace Add a spec descriptor for resourceName Add a spec descriptor for ipam Add a spec descriptor for vlan Add a spec descriptor for ipam Add a spec descriptor for networkNamespace Add a spec descriptor for resourceName Add a spec descriptor for spoofChk Add a spec descriptor for trust Add a spec descriptor for resourceName Add a spec descriptor for deviceType Add a spec descriptor for mtu Add a spec descriptor for nicSelector Add a spec descriptor for nodeSelector Add a spec descriptor for numVfs Add a spec descriptor for priority Add a spec descriptor for interfaces Add a spec descriptor for foo Add a spec descriptor for enableInjector Add a spec descriptor for enableOperatorWebhook Add a spec descriptor for logLevel	CHECK THE WARNINGS (+) For sriov-network-operator.4.11.0-202208301406: Warning: Value sriov-network-operator.4.11.0-202208301406: unable to find the resource requests for the container: (sriov-network-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value sriov-network-operator.4.11.0-202208301406: owned CRD "sriovnetworkpoolconfigs.sriovnetwork.openshift.io" has an empty description Warning: Value sriov-network-operator.4.11.0-202208301406: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value sriov-network-operator.4.11.0-202208301406: csv.metadata.Name sriov-network-operator.4.11.0-202208301406 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (sriov-network-operator.4.11.0-202208301406) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For sriov-network-operator.4.11.0-202208301406: Warning: Value sriov-network-operator.4.11.0-202208301406: unable to find the resource requests for the container: (sriov-network-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value sriov-network-operator.4.11.0-202208301406: owned CRD "sriovnetworkpoolconfigs.sriovnetwork.openshift.io" has an empty description Warning: Value sriov-network-operator.4.11.0-202208301406: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value sriov-network-operator.4.11.0-202208301406: csv.metadata.Name sriov-network-operator.4.11.0-202208301406 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (sriov-network-operator.4.11.0-202208301406) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
odf-multicluster-orchestrator	PROBABLY COMPLY Following those complies: stable-4.10 stable-4.11	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For odf-multicluster-orchestrator.v4.10.5: Owned CRDs do not have resources specified items does not have a spec descriptor manageS3 does not have a spec descriptor schedulingIntervals does not have a spec descriptor mirrorpeers.multicluster.odf.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for items Add a spec descriptor for manageS3 Add a spec descriptor for schedulingIntervals For odf-multicluster-orchestrator.v4.11.1: items does not have a spec descriptor manageS3 does not have a spec descriptor schedulingIntervals does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for items Add a spec descriptor for manageS3 Add a spec descriptor for schedulingIntervals mirrorpeers.multicluster.odf.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For odf-multicluster-orchestrator.v4.10.5: Warning: Value : (odf-multicluster-orchestrator.v4.10.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For odf-multicluster-orchestrator.v4.11.1: Warning: Value odf-multicluster-orchestrator.v4.11.1: unable to find the resource requests for the container: (odf-multicluster-console). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (odf-multicluster-orchestrator.v4.11.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
tang-operator	NOT COMPLY Following those does NOT complies: (+) . 0.0.24	SHOULD SUPPORT	PASSED IN ALL CHECKS	PASSED IN ALL CHECKS	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
volsync-product	NOT COMPLY Following those does NOT complies: (+) . acm-2.6 acm-2.5 Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For volsync-product.v0.5.0: Owned CRDs do not have resources specified rsync does not have a spec descriptor rsync does not have a spec descriptor sourcePVC does not have a spec descriptor trigger does not have a spec descriptor Add a spec descriptor for rsync Add a spec descriptor for rsync Add a spec descriptor for sourcePVC Add a spec descriptor for trigger replicationdestinations.volsync.backube does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status replicationsources.volsync.backube does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For volsync-product.v0.5.0: Owned CRDs do not have resources specified rsync does not have a spec descriptor rsync does not have a spec descriptor sourcePVC does not have a spec descriptor trigger does not have a spec descriptor Add a spec descriptor for rsync Add a spec descriptor for rsync Add a spec descriptor for sourcePVC Add a spec descriptor for trigger replicationdestinations.volsync.backube does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status replicationsources.volsync.backube does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For volsync-product.v0.4.2: rsync does not have a spec descriptor rsync does not have a spec descriptor sourcePVC does not have a spec descriptor trigger does not have a spec descriptor Owned CRDs do not have resources specified replicationdestinations.volsync.backube does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status replicationsources.volsync.backube does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for rsync Add a spec descriptor for rsync Add a spec descriptor for sourcePVC Add a spec descriptor for trigger	CHECK THE WARNINGS (+) For volsync-product.v0.5.0: Warning: Value volsync-product.v0.5.0: channel(s) ["acm-2.6"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For volsync-product.v0.5.0: Warning: Value volsync-product.v0.5.0: channel(s) ["acm-2.6"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For volsync-product.v0.4.2: Warning: Value volsync-product.v0.4.2: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value volsync-product.v0.4.2: channel(s) ["acm-2.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Platform Plus" "Red Hat Advanced Cluster Management for Kubernetes"	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
ansible-automation-platform-operator	PROBABLY COMPLY Following those complies: stable-2.2 stable-2.2-cluster-scoped	USED	FIX ERRORS AND WARNINGS (+) For aap-operator.v2.2.1-0.1661981661: Owned CRDs do not have resources specified Warning: Value tower.ansible.com/v1alpha1, Kind=JobTemplate: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerBackup: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerRestore: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationController: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubBackup: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubRestore: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHub: provided API should have an example annotation Warning: Value tower.ansible.com/v1alpha1, Kind=AnsibleJob: provided API should have an example annotation For aap-operator.v2.2.1-0.1661982152: Owned CRDs do not have resources specified Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubRestore: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHub: provided API should have an example annotation Warning: Value tower.ansible.com/v1alpha1, Kind=AnsibleJob: provided API should have an example annotation Warning: Value tower.ansible.com/v1alpha1, Kind=JobTemplate: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerBackup: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerRestore: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationController: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubBackup: provided API should have an example annotation	CHECK THE WARNINGS (+) For aap-operator.v2.2.1-0.1661981661: Warning: Value aap-operator.v2.2.1-0.1661981661: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aap-operator.v2.2.1-0.1661981661: unable to find the resource requests for the container: (platform-resource-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aap-operator.v2.2.1-0.1661981661: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aap-operator.v2.2.1-0.1661981661: unable to find the resource requests for the container: (automation-controller-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (aap-operator.v2.2.1-0.1661981661) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationController: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubBackup: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubRestore: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHub: provided API should have an example annotation Warning: Value tower.ansible.com/v1alpha1, Kind=AnsibleJob: provided API should have an example annotation Warning: Value tower.ansible.com/v1alpha1, Kind=JobTemplate: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerBackup: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerRestore: provided API should have an example annotation For aap-operator.v2.2.1-0.1661982152: Warning: Value aap-operator.v2.2.1-0.1661982152: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aap-operator.v2.2.1-0.1661982152: unable to find the resource requests for the container: (platform-resource-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aap-operator.v2.2.1-0.1661982152: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aap-operator.v2.2.1-0.1661982152: unable to find the resource requests for the container: (automation-controller-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (aap-operator.v2.2.1-0.1661982152) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value tower.ansible.com/v1alpha1, Kind=JobTemplate: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerBackup: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationControllerRestore: provided API should have an example annotation Warning: Value automationcontroller.ansible.com/v1beta1, Kind=AutomationController: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubBackup: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHubRestore: provided API should have an example annotation Warning: Value automationhub.ansible.com/v1beta1, Kind=AutomationHub: provided API should have an example annotation Warning: Value tower.ansible.com/v1alpha1, Kind=AnsibleJob: provided API should have an example annotation	[Full Lifecycle]	NOT ADDED	RBAC requested for the API(s): (All from apiGroups): batch/* (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
bare-metal-event-relay	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	SHOULD SUPPORT	CHECK THE WARNINGS (+) For bare-metal-event-relay.v4.11.0: hardwareevents.event.redhat-cne.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For bare-metal-event-relay.v4.11.0: hardwareevents.event.redhat-cne.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For bare-metal-event-relay.v4.11.0: Warning: Value bare-metal-event-relay.v4.11.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value bare-metal-event-relay.v4.11.0: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (bare-metal-event-relay.v4.11.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For bare-metal-event-relay.v4.11.0: Warning: Value bare-metal-event-relay.v4.11.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value bare-metal-event-relay.v4.11.0: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (bare-metal-event-relay.v4.11.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
dpu-network-operator	PROBABLY COMPLY Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For dpu-network-operator.4.11.0-202208291725: kubeConfigFile does not have a spec descriptor nodeSelector does not have a spec descriptor poolName does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for kubeConfigFile Add a spec descriptor for nodeSelector Add a spec descriptor for poolName ovnkubeconfigs.dpu.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For dpu-network-operator.4.11.0-202208291725: Warning: Value dpu-network-operator.4.11.0-202208291725: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value dpu-network-operator.4.11.0-202208291725: csv.metadata.Name dpu-network-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (dpu-network-operator.4.11.0-202208291725) csv.Spec.Icon not specified Warning: Value : (dpu-network-operator.4.11.0-202208291725) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
integration-operator	NOT COMPLY Following those does NOT complies: (+) . 1.x	SHOULD SUPPORT	CHECK THE WARNINGS (+) For integration-operator.v1.3.0-0.1648516199.p: installations.integration.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For integration-operator.v1.3.0-0.1648516199.p: Warning: Value integration-operator.v1.3.0-0.1648516199.p: channel(s) ["1.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (integration-operator.v1.3.0-0.1648516199.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
kiali-ossm	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For kiali-operator.v1.48.2: installation_tag does not have a spec descriptor istio_namespace does not have a spec descriptor deployment does not have a spec descriptor items does not have a spec descriptor Owned CRDs do not have resources specified Add CRD validation for spec field `installation_tag` in Kiali/v1alpha1 Add CRD validation for spec field `istio_namespace` in Kiali/v1alpha1 Add CRD validation for spec field `deployment` in Kiali/v1alpha1 Add CRD validation for spec field `title` in MonitoringDashboard/v1alpha1 Add CRD validation for spec field `items` in MonitoringDashboard/v1alpha1 Add a spec descriptor for installation_tag Add a spec descriptor for istio_namespace Add a spec descriptor for deployment Add a spec descriptor for items kialis.kiali.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status monitoringdashboards.monitoring.kiali.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For kiali-operator.v1.48.2: Warning: Value : (kiali-operator.v1.48.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Deep Insights]	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (apiGroups/resources): autoscaling/horizontalpodautoscalers (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
businessautomation-operator	PROBABLY COMPLY Following those complies: stable	USED	CHECK THE WARNINGS (+) For businessautomation-operator.7.12.1-3: kieapps.app.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For businessautomation-operator.7.12.1-3: Warning: Value businessautomation-operator.7.12.1-3: unable to find the resource requests for the container: (business-automation-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value businessautomation-operator.7.12.1-3: csv.metadata.Name businessautomation-operator.7.12.1-3 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (businessautomation-operator.7.12.1-3) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		NOT USED	NOT USED
eap	PROBABLY COMPLY Following those complies: stable	SHOULD SUPPORT	CHECK THE WARNINGS (+) For eap-operator.v2.3.5: Warning: Value : (eap-operator.v2.3.5) example annotations not found	CHECK THE WARNINGS (+) For eap-operator.v2.3.5: Warning: Value eap-operator.v2.3.5: unable to find the resource requests for the container: (eap-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (eap-operator.v2.3.5) example annotations not found	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"Red Hat JBoss Enterprise Application Platform" "Red Hat Runtimes" "Red Hat Integration" "Red Hat Process Automation"		NOT USED	NOT USED
mtv-operator	NOT COMPLY Following those does NOT complies: (+) . release-v2.3.0 release-v2.3 release-v2.1.0 release-v2.2.0	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For mtv-operator.v2.3.2: feature_validation does not have a spec descriptor feature_must_gather_api does not have a spec descriptor feature_ui does not have a spec descriptor plan does not have a spec descriptor type does not have a spec descriptor secret does not have a spec descriptor url does not have a spec descriptor provider does not have a spec descriptor id does not have a spec descriptor ipAddress does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor image does not have a spec descriptor playbook does not have a spec descriptor Owned CRDs do not have resources specified Add CRD validation for spec field `feature_ui` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_validation` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_must_gather_api` in ForkliftController/v1beta1 Add a spec descriptor for feature_validation Add a spec descriptor for feature_must_gather_api Add a spec descriptor for feature_ui Add a spec descriptor for plan Add a spec descriptor for type Add a spec descriptor for secret Add a spec descriptor for url Add a spec descriptor for provider Add a spec descriptor for id Add a spec descriptor for ipAddress Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for image Add a spec descriptor for playbook forkliftcontrollers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migrations.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status plans.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status providers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hosts.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status networkmaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status storagemaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hooks.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For mtv-operator.2.1.0: feature_ui does not have a spec descriptor feature_validation does not have a spec descriptor plan does not have a spec descriptor type does not have a spec descriptor secret does not have a spec descriptor url does not have a spec descriptor provider does not have a spec descriptor id does not have a spec descriptor ipAddress does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor image does not have a spec descriptor playbook does not have a spec descriptor name does not have a spec descriptor volumeModes does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for feature_ui Add a spec descriptor for feature_validation Add a spec descriptor for plan Add a spec descriptor for type Add a spec descriptor for secret Add a spec descriptor for url Add a spec descriptor for provider Add a spec descriptor for id Add a spec descriptor for ipAddress Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for image Add a spec descriptor for playbook Add a spec descriptor for name Add a spec descriptor for volumeModes Add CRD validation for spec field `feature_ui` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_validation` in ForkliftController/v1beta1 forkliftcontrollers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migrations.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status plans.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status providers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hosts.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status networkmaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status storagemaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hooks.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status provisioners.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For mtv-operator.v2.2.0: feature_ui does not have a spec descriptor feature_validation does not have a spec descriptor feature_must_gather_api does not have a spec descriptor plan does not have a spec descriptor type does not have a spec descriptor secret does not have a spec descriptor url does not have a spec descriptor provider does not have a spec descriptor id does not have a spec descriptor ipAddress does not have a spec descriptor map does not have a spec descriptor provider does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor image does not have a spec descriptor playbook does not have a spec descriptor name does not have a spec descriptor volumeModes does not have a spec descriptor Owned CRDs do not have resources specified Add CRD validation for spec field `feature_ui` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_validation` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_must_gather_api` in ForkliftController/v1beta1 forkliftcontrollers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migrations.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status plans.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status providers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hosts.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status networkmaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status storagemaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hooks.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status provisioners.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for feature_ui Add a spec descriptor for feature_validation Add a spec descriptor for feature_must_gather_api Add a spec descriptor for plan Add a spec descriptor for type Add a spec descriptor for secret Add a spec descriptor for url Add a spec descriptor for provider Add a spec descriptor for id Add a spec descriptor for ipAddress Add a spec descriptor for map Add a spec descriptor for provider Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for image Add a spec descriptor for playbook Add a spec descriptor for name Add a spec descriptor for volumeModes For mtv-operator.v2.3.2: feature_validation does not have a spec descriptor feature_must_gather_api does not have a spec descriptor feature_ui does not have a spec descriptor plan does not have a spec descriptor type does not have a spec descriptor secret does not have a spec descriptor url does not have a spec descriptor provider does not have a spec descriptor id does not have a spec descriptor ipAddress does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor provider does not have a spec descriptor map does not have a spec descriptor image does not have a spec descriptor playbook does not have a spec descriptor Owned CRDs do not have resources specified Add CRD validation for spec field `feature_ui` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_validation` in ForkliftController/v1beta1 Add CRD validation for spec field `feature_must_gather_api` in ForkliftController/v1beta1 Add a spec descriptor for feature_validation Add a spec descriptor for feature_must_gather_api Add a spec descriptor for feature_ui Add a spec descriptor for plan Add a spec descriptor for type Add a spec descriptor for secret Add a spec descriptor for url Add a spec descriptor for provider Add a spec descriptor for id Add a spec descriptor for ipAddress Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for provider Add a spec descriptor for map Add a spec descriptor for image Add a spec descriptor for playbook forkliftcontrollers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status migrations.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status plans.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status providers.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hosts.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status networkmaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status storagemaps.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hooks.forklift.konveyor.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For mtv-operator.v2.3.2: Warning: Value mtv-operator.v2.3.2: unable to find the resource requests for the container: (forklift-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mtv-operator.v2.3.2: channel(s) ["release-v2.3.0" "release-v2.3"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For mtv-operator.2.1.0: Warning: Value mtv-operator.2.1.0: unable to find the resource requests for the container: (forklift-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mtv-operator.2.1.0: channel(s) ["release-v2.1.0"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value mtv-operator.2.1.0: csv.metadata.Name mtv-operator.2.1.0 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For mtv-operator.v2.2.0: Warning: Value mtv-operator.v2.2.0: unable to find the resource requests for the container: (forklift-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mtv-operator.v2.2.0: channel(s) ["release-v2.2.0"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For mtv-operator.v2.3.2: Warning: Value mtv-operator.v2.3.2: unable to find the resource requests for the container: (forklift-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mtv-operator.v2.3.2: channel(s) ["release-v2.3.0" "release-v2.3"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		NOT USED	NOT USED
odr-hub-operator	PROBABLY COMPLY Following those complies: stable-4.11 stable-4.10	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For odr-hub-operator.v4.11.1: s3ProfileName does not have a spec descriptor region does not have a spec descriptor placementRef does not have a spec descriptor preferredCluster does not have a spec descriptor pvcSelector does not have a spec descriptor drPolicyRef does not have a spec descriptor drClusters does not have a spec descriptor replicationClassSelector does not have a spec descriptor schedulingInterval does not have a spec descriptor drClusters does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for s3ProfileName Add a spec descriptor for region Add a spec descriptor for placementRef Add a spec descriptor for preferredCluster Add a spec descriptor for pvcSelector Add a spec descriptor for drPolicyRef Add a spec descriptor for drClusters Add a spec descriptor for replicationClassSelector Add a spec descriptor for schedulingInterval Add a spec descriptor for drClusters drclusters.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status drplacementcontrols.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status drpolicies.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status drpolicies.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For odr-hub-operator.v4.10.5: Owned CRDs do not have resources specified drPolicyRef does not have a spec descriptor placementRef does not have a spec descriptor preferredCluster does not have a spec descriptor pvcSelector does not have a spec descriptor drClusterSet does not have a spec descriptor replicationClassSelector does not have a spec descriptor schedulingInterval does not have a spec descriptor drClusterSet does not have a spec descriptor drplacementcontrols.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status drpolicies.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status drpolicies.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for drPolicyRef Add a spec descriptor for placementRef Add a spec descriptor for preferredCluster Add a spec descriptor for pvcSelector Add a spec descriptor for drClusterSet Add a spec descriptor for replicationClassSelector Add a spec descriptor for schedulingInterval Add a spec descriptor for drClusterSet	CHECK THE WARNINGS (+) For odr-hub-operator.v4.11.1: Warning: Value odr-hub-operator.v4.11.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (odr-hub-operator.v4.11.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For odr-hub-operator.v4.10.5: Warning: Value odr-hub-operator.v4.10.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (odr-hub-operator.v4.10.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
topology-aware-lifecycle-manager	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	USED	CHECK THE WARNINGS (+) For topology-aware-lifecycle-manager.v4.11.0: clustergroupupgrades.ran.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For topology-aware-lifecycle-manager.v4.11.0: clustergroupupgrades.ran.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For topology-aware-lifecycle-manager.v4.11.0: Warning: Value topology-aware-lifecycle-manager.v4.11.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value topology-aware-lifecycle-manager.v4.11.0: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (topology-aware-lifecycle-manager.v4.11.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For topology-aware-lifecycle-manager.v4.11.0: Warning: Value topology-aware-lifecycle-manager.v4.11.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value topology-aware-lifecycle-manager.v4.11.0: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (topology-aware-lifecycle-manager.v4.11.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
amq-online	PROBABLY COMPLY Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For amq-online.1.7.4-0.1657725339.p: broker does not have a spec descriptor router does not have a spec descriptor broker does not have a spec descriptor addressType does not have a spec descriptor resources does not have a spec descriptor addressSpaceType does not have a spec descriptor resourceLimits does not have a spec descriptor addressPlans does not have a spec descriptor standard does not have a spec descriptor address does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for broker Add a spec descriptor for router Add a spec descriptor for broker Add a spec descriptor for addressType Add a spec descriptor for resources Add a spec descriptor for addressSpaceType Add a spec descriptor for resourceLimits Add a spec descriptor for addressPlans Add a spec descriptor for standard Add a spec descriptor for address Add a spec descriptor for authentication Add a spec descriptor for authorization Warning: Value enmasse.io/v1beta1, Kind=AddressSpaceSchema: provided API should have an example annotation Warning: Value admin.enmasse.io/v1beta1, Kind=ConsoleService: provided API should have an example annotation standardinfraconfigs.admin.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status brokeredinfraconfigs.admin.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status addressplans.admin.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status addressspaceplans.admin.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status authenticationservices.admin.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status addressspaces.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status addresses.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status messagingusers.user.enmasse.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For amq-online.1.7.4-0.1657725339.p: Warning: Value amq-online.1.7.4-0.1657725339.p: unable to find the resource requests for the container: (controller). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amq-online.1.7.4-0.1657725339.p: csv.metadata.Name amq-online.1.7.4-0.1657725339.p is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (amq-online.1.7.4-0.1657725339.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value admin.enmasse.io/v1beta1, Kind=ConsoleService: provided API should have an example annotation Warning: Value enmasse.io/v1beta1, Kind=AddressSpaceSchema: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"Red Hat Integration" "Red Hat AMQ"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
ansible-cloud-addons-operator	PROBABLY COMPLY Following those complies: stable-2.2-cluster-scoped stable-cluster-scoped	USED	FIX ERRORS AND WARNINGS (+) For aca-operator.v2.2.1-0.1661979097: Owned CRDs do not have resources specified Warning: Value platform.ansible.com/v1alpha1, Kind=AnsibleAutomationPlatformAwsBilling: provided API should have an example annotation Warning: Value platform.ansible.com/v1alpha1, Kind=AnsibleAutomationPlatformAzureBilling: provided API should have an example annotation Warning: Value platform.ansible.com/v1alpha1, Kind=AutomationPlatform: provided API should have an example annotation For aca-operator.v2.1.1-0.1645829566: Owned CRDs do not have resources specified Warning: Value platform.ansible.com/v1alpha1, Kind=AnsibleAutomationPlatformAzureBilling: provided API should have an example annotation Warning: Value platform.ansible.com/v1alpha1, Kind=AutomationPlatform: provided API should have an example annotation	CHECK THE WARNINGS (+) For aca-operator.v2.2.1-0.1661979097: Warning: Value aca-operator.v2.2.1-0.1661979097: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aca-operator.v2.2.1-0.1661979097: unable to find the resource requests for the container: (aap-billing-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aca-operator.v2.2.1-0.1661979097: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aca-operator.v2.2.1-0.1661979097: unable to find the resource requests for the container: (aap-ui-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (aca-operator.v2.2.1-0.1661979097) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value platform.ansible.com/v1alpha1, Kind=AnsibleAutomationPlatformAwsBilling: provided API should have an example annotation Warning: Value platform.ansible.com/v1alpha1, Kind=AnsibleAutomationPlatformAzureBilling: provided API should have an example annotation Warning: Value platform.ansible.com/v1alpha1, Kind=AutomationPlatform: provided API should have an example annotation For aca-operator.v2.1.1-0.1645829566: Warning: Value aca-operator.v2.1.1-0.1645829566: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aca-operator.v2.1.1-0.1645829566: unable to find the resource requests for the container: (aap-azure-billing-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aca-operator.v2.1.1-0.1645829566: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value aca-operator.v2.1.1-0.1645829566: unable to find the resource requests for the container: (aap-ui-manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (aca-operator.v2.1.1-0.1645829566) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value platform.ansible.com/v1alpha1, Kind=AutomationPlatform: provided API should have an example annotation Warning: Value platform.ansible.com/v1alpha1, Kind=AnsibleAutomationPlatformAzureBilling: provided API should have an example annotation	[Full Lifecycle]	"Red Hat Ansible Automation Platform"	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
cryostat-operator	PROBABLY COMPLY Following those complies: stable stable-2.0	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For cryostat-operator.v2.1.1-2.1659469835.p: flightRecorder does not have a spec descriptor Add a spec descriptor for flightRecorder cryostats.operator.cryostat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status flightrecorders.operator.cryostat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status recordings.operator.cryostat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For cryostat-operator.v2.0.0-6.1647887957.p: flightRecorder does not have a spec descriptor Add a spec descriptor for flightRecorder cryostats.operator.cryostat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status flightrecorders.operator.cryostat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status recordings.operator.cryostat.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For cryostat-operator.v2.1.1-2.1659469835.p: Warning: Value cryostat-operator.v2.1.1-2.1659469835.p: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (cryostat-operator.v2.1.1-2.1659469835.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For cryostat-operator.v2.0.0-6.1647887957.p: Warning: Value cryostat-operator.v2.0.0-6.1647887957.p: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (cryostat-operator.v2.0.0-6.1647887957.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"Red Hat build of OpenJDK"		USED	NOT USED
jaeger-product	PROBABLY COMPLY Following those complies: stable	USED	CHECK THE WARNINGS (+) For jaeger-operator.v1.36.0-2: jaegers.jaegertracing.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For jaeger-operator.v1.36.0-2: Warning: Value : (jaeger-operator.v1.36.0-2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Deep Insights]	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): autoscaling/horizontalpodautoscalers (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
kubernetes-nmstate-operator	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For kubernetes-nmstate-operator.4.11.0-202208300306: Owned CRDs do not have resources specified error spec does not exist for the custom resource nmstate nmstates.nmstate.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [nmstate] For kubernetes-nmstate-operator.4.11.0-202208300306: Owned CRDs do not have resources specified error spec does not exist for the custom resource nmstate nmstates.nmstate.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [nmstate]	CHECK THE WARNINGS (+) For kubernetes-nmstate-operator.4.11.0-202208300306: Warning: Value kubernetes-nmstate-operator.4.11.0-202208300306: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value kubernetes-nmstate-operator.4.11.0-202208300306: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value kubernetes-nmstate-operator.4.11.0-202208300306: csv.metadata.Name kubernetes-nmstate-operator.4.11.0-202208300306 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (kubernetes-nmstate-operator.4.11.0-202208300306) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For kubernetes-nmstate-operator.4.11.0-202208300306: Warning: Value kubernetes-nmstate-operator.4.11.0-202208300306: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value kubernetes-nmstate-operator.4.11.0-202208300306: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value kubernetes-nmstate-operator.4.11.0-202208300306: csv.metadata.Name kubernetes-nmstate-operator.4.11.0-202208300306 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (kubernetes-nmstate-operator.4.11.0-202208300306) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
cluster-kube-descheduler-operator	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For clusterkubedescheduleroperator.4.11.0-202208291725: deschedulingIntervalSeconds does not have a spec descriptor managementState does not have a spec descriptor mode does not have a spec descriptor profiles does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for deschedulingIntervalSeconds Add a spec descriptor for managementState Add a spec descriptor for mode Add a spec descriptor for profiles kubedeschedulers.operator.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For clusterkubedescheduleroperator.4.11.0-202208291725: deschedulingIntervalSeconds does not have a spec descriptor managementState does not have a spec descriptor mode does not have a spec descriptor profiles does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for deschedulingIntervalSeconds Add a spec descriptor for managementState Add a spec descriptor for mode Add a spec descriptor for profiles kubedeschedulers.operator.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For clusterkubedescheduleroperator.4.11.0-202208291725: Warning: Value clusterkubedescheduleroperator.4.11.0-202208291725: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value clusterkubedescheduleroperator.4.11.0-202208291725: csv.metadata.Name clusterkubedescheduleroperator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For clusterkubedescheduleroperator.4.11.0-202208291725: Warning: Value clusterkubedescheduleroperator.4.11.0-202208291725: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value clusterkubedescheduleroperator.4.11.0-202208291725: csv.metadata.Name clusterkubedescheduleroperator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		NOT USED	NOT USED
metallb-operator	PROBABLY COMPLY Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For metallb-operator.4.11.0-202208300306: error spec does not exist for the custom resource metallb Owned CRDs do not have resources specified receiveInterval does not have a spec descriptor transmitInterval does not have a spec descriptor ipAddressPools does not have a spec descriptor peers does not have a spec descriptor ipAddressPoolSelectors does not have a spec descriptor aggregationLength does not have a spec descriptor aggregationLengthV6 does not have a spec descriptor communities does not have a spec descriptor ipAddressPools does not have a spec descriptor localPref does not have a spec descriptor communities does not have a spec descriptor ipAddressPools does not have a spec descriptor localPref does not have a spec descriptor aggregationLength does not have a spec descriptor aggregationLengthV6 does not have a spec descriptor aggregationLength does not have a spec descriptor aggregationLengthV6 does not have a spec descriptor ipAddressPools does not have a spec descriptor nodeSelectors does not have a spec descriptor communities does not have a spec descriptor addresses does not have a spec descriptor addresses does not have a spec descriptor autoAssign does not have a spec descriptor addresses does not have a spec descriptor ipAddressPools does not have a spec descriptor nodeSelectors does not have a spec descriptor peerASN does not have a spec descriptor peerAddress does not have a spec descriptor myASN does not have a spec descriptor myASN does not have a spec descriptor peerASN does not have a spec descriptor peerAddress does not have a spec descriptor bfdProfile does not have a spec descriptor holdTime does not have a spec descriptor keepaliveTime does not have a spec descriptor myASN does not have a spec descriptor passwordSecret does not have a spec descriptor peerASN does not have a spec descriptor peerAddress does not have a spec descriptor peerPort does not have a spec descriptor Warning: Value metallb.io/v1alpha1, Kind=AddressPool: provided API should have an example annotation Warning: Value metallb.io/v1beta1, Kind=BGPPeer: provided API should have an example annotation Warning: Value metallb.io/v1beta1, Kind=AddressPool: provided API should have an example annotation bfdprofiles.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgpadvertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgpadvertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgpadvertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgpadvertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgpadvertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status communities.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ipaddresspools.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ipaddresspools.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ipaddresspools.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status l2advertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status l2advertisements.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status metallbs.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgppeers.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgppeers.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status bgppeers.metallb.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [metallb] Add a spec descriptor for receiveInterval Add a spec descriptor for transmitInterval Add a spec descriptor for ipAddressPools Add a spec descriptor for peers Add a spec descriptor for ipAddressPoolSelectors Add a spec descriptor for aggregationLength Add a spec descriptor for aggregationLengthV6 Add a spec descriptor for communities Add a spec descriptor for ipAddressPools Add a spec descriptor for localPref Add a spec descriptor for communities Add a spec descriptor for ipAddressPools Add a spec descriptor for localPref Add a spec descriptor for aggregationLength Add a spec descriptor for aggregationLengthV6 Add a spec descriptor for aggregationLength Add a spec descriptor for aggregationLengthV6 Add a spec descriptor for ipAddressPools Add a spec descriptor for nodeSelectors Add a spec descriptor for communities Add a spec descriptor for addresses Add a spec descriptor for addresses Add a spec descriptor for autoAssign Add a spec descriptor for addresses Add a spec descriptor for ipAddressPools Add a spec descriptor for nodeSelectors Add a spec descriptor for peerASN Add a spec descriptor for peerAddress Add a spec descriptor for myASN Add a spec descriptor for myASN Add a spec descriptor for peerASN Add a spec descriptor for peerAddress Add a spec descriptor for bfdProfile Add a spec descriptor for holdTime Add a spec descriptor for keepaliveTime Add a spec descriptor for myASN Add a spec descriptor for passwordSecret Add a spec descriptor for peerASN Add a spec descriptor for peerAddress Add a spec descriptor for peerPort	CHECK THE WARNINGS (+) For metallb-operator.4.11.0-202208300306: Warning: Value metallb-operator.4.11.0-202208300306: unable to find the resource requests for the container: (webhook-server). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "addresspools.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "addresspools.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "bfdprofiles.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "bgpadvertisements.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "bgppeers.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "bgppeers.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "communities.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "ipaddresspools.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: owned CRD "l2advertisements.metallb.io" has an empty description Warning: Value metallb-operator.4.11.0-202208300306: csv.metadata.Name metallb-operator.4.11.0-202208300306 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (metallb-operator.4.11.0-202208300306) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value metallb.io/v1beta1, Kind=BGPPeer: provided API should have an example annotation Warning: Value metallb.io/v1alpha1, Kind=AddressPool: provided API should have an example annotation Warning: Value metallb.io/v1beta1, Kind=AddressPool: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/podsecuritypolicies (apiGroups/resources): discovery.k8s.io/endpointslices (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
node-observability-operator	NOT COMPLY Following those does NOT complies: (+) . alpha	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For node-observability-operator.v0.1.0: Owned CRDs do not have resources specified type does not have a spec descriptor labels does not have a spec descriptor debug does not have a spec descriptor nodeObservabilityRef does not have a spec descriptor nodeobservabilities.nodeobservability.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status nodeobservabilitymachineconfigs.nodeobservability.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status nodeobservabilityruns.nodeobservability.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for type Add a spec descriptor for labels Add a spec descriptor for debug Add a spec descriptor for nodeObservabilityRef	CHECK THE WARNINGS (+) For node-observability-operator.v0.1.0: Warning: Value node-observability-operator.v0.1.0: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform"		USED	NOT USED
ptp-operator	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For ptp-operator.4.11.0-202208291725: profile does not have a spec descriptor recommend does not have a spec descriptor daemonNodeSelector does not have a spec descriptor ptpEventConfig does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for profile Add a spec descriptor for recommend Add a spec descriptor for daemonNodeSelector Add a spec descriptor for ptpEventConfig nodeptpdevices.ptp.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ptpconfigs.ptp.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ptpoperatorconfigs.ptp.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For ptp-operator.4.11.0-202208291725: Warning: Value ptp-operator.4.11.0-202208291725: csv.metadata.Name ptp-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (ptp-operator.4.11.0-202208291725) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
odr-cluster-operator	PROBABLY COMPLY Following those complies: stable-4.10 stable-4.11	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For odr-cluster-operator.v4.10.5: async does not have a spec descriptor pvcSelector does not have a spec descriptor replicationState does not have a spec descriptor s3ProfileNames does not have a spec descriptor Owned CRDs do not have resources specified Add CRD validation for spec field `s3ProfileNames` in VolumeReplicationGroup/v1alpha1 Add a spec descriptor for async Add a spec descriptor for pvcSelector Add a spec descriptor for replicationState Add a spec descriptor for s3ProfileNames volumereplicationgroups.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For odr-cluster-operator.v4.11.1: async does not have a spec descriptor pvcSelector does not have a spec descriptor replicationState does not have a spec descriptor s3ProfileNames does not have a spec descriptor Owned CRDs do not have resources specified volumereplicationgroups.ramendr.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for async Add a spec descriptor for pvcSelector Add a spec descriptor for replicationState Add a spec descriptor for s3ProfileNames Add CRD validation for spec field `s3ProfileNames` in VolumeReplicationGroup/v1alpha1	CHECK THE WARNINGS (+) For odr-cluster-operator.v4.10.5: Warning: Value odr-cluster-operator.v4.10.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (odr-cluster-operator.v4.10.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For odr-cluster-operator.v4.11.1: Warning: Value odr-cluster-operator.v4.11.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (odr-cluster-operator.v4.11.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
openshift-custom-metrics-autoscaler-operator	PROBABLY COMPLY Following those complies: stable	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. custom-metrics-autoscaler.v2.7.1	FIX ERRORS AND WARNINGS (+) For custom-metrics-autoscaler.v2.7.1: operator does not have a spec descriptor metricsServer does not have a spec descriptor serviceAccount does not have a spec descriptor triggers does not have a spec descriptor kedacontrollers.keda.sh does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status scaledjobs.keda.sh does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status scaledobjects.keda.sh does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status triggerauthentications.keda.sh does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status clustertriggerauthentications.keda.sh does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for operator Add a spec descriptor for metricsServer Add a spec descriptor for serviceAccount Add a spec descriptor for triggers	PASSED IN ALL CHECKS	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
quay-operator	NOT COMPLY Following those does NOT complies: (+) . quay-v3.4 quay-v3.5 Following those complies: stable-3.7 stable-3.6	USED	FIX ERRORS AND WARNINGS (+) For quay-operator.v3.4.7: Owned CRDs do not have resources specified quayregistries.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation For quay-operator.v3.5.7: Owned CRDs do not have resources specified quayregistries.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation For quay-operator.v3.7.8: Owned CRDs do not have resources specified quayregistries.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation For quay-operator.v3.6.10: Owned CRDs do not have resources specified Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation quayregistries.quay.redhat.com does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For quay-operator.v3.4.7: Warning: Value quay-operator.v3.4.7: unable to find the resource requests for the container: (quay-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value quay-operator.v3.4.7: channel(s) ["quay-v3.4"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (quay-operator.v3.4.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation For quay-operator.v3.5.7: Warning: Value quay-operator.v3.5.7: unable to find the resource requests for the container: (quay-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value quay-operator.v3.5.7: channel(s) ["quay-v3.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (quay-operator.v3.5.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation For quay-operator.v3.7.8: Warning: Value quay-operator.v3.7.8: unable to find the resource requests for the container: (quay-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (quay-operator.v3.7.8) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation For quay-operator.v3.6.10: Warning: Value quay-operator.v3.6.10: unable to find the resource requests for the container: (quay-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (quay-operator.v3.6.10) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value redhatcop.redhat.io/v1alpha1, Kind=QuayEcosystem: provided API should have an example annotation	[Full Lifecycle]	"OpenShift Platform Plus" "Red Hat Quay"	RBAC requested for the API(s): (apiGroups/resources): autoscaling/horizontalpodautoscalers (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
bamoe-kogito-operator	NOT COMPLY Following those does NOT complies: (+) . 8.x	SHOULD SUPPORT	CHECK THE WARNINGS (+) For bamoe-kogito-operator.8.0.0-1: kogitobuilds.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kogitoinfras.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kogitoruntimes.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kogitosupportingservices.rhpam.kiegroup.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For bamoe-kogito-operator.8.0.0-1: Warning: Value bamoe-kogito-operator.8.0.0-1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value bamoe-kogito-operator.8.0.0-1: channel(s) ["8.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value bamoe-kogito-operator.8.0.0-1: csv.metadata.Name bamoe-kogito-operator.8.0.0-1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (bamoe-kogito-operator.8.0.0-1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
devspaces	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For devspacesoperator.v3.1.0: server does not have a spec descriptor storage does not have a spec descriptor auth does not have a spec descriptor database does not have a spec descriptor k8s does not have a spec descriptor metrics does not have a spec descriptor Add a spec descriptor for server Add a spec descriptor for storage Add a spec descriptor for auth Add a spec descriptor for database Add a spec descriptor for k8s Add a spec descriptor for metrics checlusters.org.eclipse.che does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status checlusters.org.eclipse.che does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For devspacesoperator.v3.1.0: Warning: Value devspacesoperator.v3.1.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (devspacesoperator.v3.1.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
mcg-operator	PROBABLY COMPLY Following those complies: stable-4.11 stable-4.10	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For mcg-operator.v4.11.1: backingstores.noobaa.io does not have a status descriptor namespacestores.noobaa.io does not have a status descriptor cleanupPolicy does not have a spec descriptor security does not have a spec descriptor type does not have a spec descriptor type does not have a spec descriptor allow_bucket_creation does not have a spec descriptor allowed_buckets does not have a spec descriptor noobaas.noobaa.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd backingstores.noobaa.io. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ add status descriptor for the crd namespacestores.noobaa.io. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ bucketclasses.noobaa.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status noobaaaccounts.noobaa.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for cleanupPolicy Add a spec descriptor for security Add a spec descriptor for type Add a spec descriptor for type Add a spec descriptor for allow_bucket_creation Add a spec descriptor for allowed_buckets For mcg-operator.v4.10.5: backingstores.noobaa.io does not have a status descriptor namespacestores.noobaa.io does not have a status descriptor cleanupPolicy does not have a spec descriptor security does not have a spec descriptor type does not have a spec descriptor type does not have a spec descriptor allow_bucket_creation does not have a spec descriptor allowed_buckets does not have a spec descriptor noobaas.noobaa.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd backingstores.noobaa.io. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ add status descriptor for the crd namespacestores.noobaa.io. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ bucketclasses.noobaa.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status noobaaaccounts.noobaa.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for cleanupPolicy Add a spec descriptor for security Add a spec descriptor for type Add a spec descriptor for type Add a spec descriptor for allow_bucket_creation Add a spec descriptor for allowed_buckets	CHECK THE WARNINGS (+) For mcg-operator.v4.11.1: Warning: Value mcg-operator.v4.11.1: unable to find the resource requests for the container: (noobaa-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mcg-operator.v4.11.1: owned CRD "noobaaaccounts.noobaa.io" has an empty description For mcg-operator.v4.10.5: Warning: Value mcg-operator.v4.10.5: unable to find the resource requests for the container: (noobaa-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value mcg-operator.v4.10.5: owned CRD "noobaaaccounts.noobaa.io" has an empty description	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): autoscaling/horizontalpodautoscalers (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
multicluster-engine	PROBABLY COMPLY Following those complies: stable-2.0 stable-2.1	USED	FIX ERRORS AND WARNINGS (+) For multicluster-engine.v2.0.2: Owned CRDs do not have resources specified multiclusterengines.multicluster.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For multicluster-engine.v2.1.1: Owned CRDs do not have resources specified multiclusterengines.multicluster.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For multicluster-engine.v2.0.2: Warning: Value multicluster-engine.v2.0.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (multicluster-engine.v2.0.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For multicluster-engine.v2.1.1: Warning: Value multicluster-engine.v2.1.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (multicluster-engine.v2.1.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
odf-csi-addons-operator	PROBABLY COMPLY Following those complies: stable-4.11 stable-4.10	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For odf-csi-addons-operator.v4.11.1: Owned CRDs do not have resources specified Warning: Value csiaddons.openshift.io/v1alpha1, Kind=CSIAddonsNode: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=NetworkFence: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceCronJob: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceJob: provided API should have an example annotation For odf-csi-addons-operator.v4.10.5: Owned CRDs do not have resources specified Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceCronJob: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceJob: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=CSIAddonsNode: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=NetworkFence: provided API should have an example annotation	CHECK THE WARNINGS (+) For odf-csi-addons-operator.v4.11.1: Warning: Value : (odf-csi-addons-operator.v4.11.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceJob: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=CSIAddonsNode: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=NetworkFence: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceCronJob: provided API should have an example annotation For odf-csi-addons-operator.v4.10.5: Warning: Value odf-csi-addons-operator.v4.10.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value : (odf-csi-addons-operator.v4.10.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value csiaddons.openshift.io/v1alpha1, Kind=CSIAddonsNode: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=NetworkFence: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceCronJob: provided API should have an example annotation Warning: Value csiaddons.openshift.io/v1alpha1, Kind=ReclaimSpaceJob: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
node-maintenance-operator	PROBABLY COMPLY Following those complies: stable	USED	CHECK THE WARNINGS (+) For node-maintenance-operator.v4.11.1: nodemaintenances.nodemaintenance.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	PASSED IN ALL CHECKS	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
redhat-oadp-operator	PROBABLY COMPLY Following those complies: stable-1.0 stable stable-1.1	USED	FIX ERRORS AND WARNINGS (+) For oadp-operator.v1.0.4: Owned CRDs do not have resources specified backupLocations does not have a spec descriptor configuration does not have a spec descriptor snapshotLocations does not have a spec descriptor Add a spec descriptor for backupLocations Add a spec descriptor for configuration Add a spec descriptor for snapshotLocations Warning: Value oadp.openshift.io/v1alpha1, Kind=CloudStorage: provided API should have an example annotation dataprotectionapplications.oadp.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backups.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backupstoragelocations.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status deletebackuprequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status downloadrequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status podvolumebackups.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status podvolumerestores.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status resticrepositories.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status restores.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status schedules.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status serverstatusrequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status volumesnapshotlocations.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For oadp-operator.v1.1.0: backupLocations does not have a spec descriptor configuration does not have a spec descriptor snapshotLocations does not have a spec descriptor Owned CRDs do not have resources specified dataprotectionapplications.oadp.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backups.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backupstoragelocations.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status deletebackuprequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status downloadrequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status podvolumebackups.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status podvolumerestores.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status resticrepositories.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status restores.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status schedules.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status serverstatusrequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status volumesnapshotlocations.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for backupLocations Add a spec descriptor for configuration Add a spec descriptor for snapshotLocations Warning: Value oadp.openshift.io/v1alpha1, Kind=CloudStorage: provided API should have an example annotation Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotBackup: provided API should have an example annotation Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotRestore: provided API should have an example annotation For oadp-operator.v1.1.0: backupLocations does not have a spec descriptor configuration does not have a spec descriptor snapshotLocations does not have a spec descriptor Owned CRDs do not have resources specified dataprotectionapplications.oadp.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backups.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backupstoragelocations.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status deletebackuprequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status downloadrequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status podvolumebackups.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status podvolumerestores.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status resticrepositories.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status restores.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status schedules.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status serverstatusrequests.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status volumesnapshotlocations.velero.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for backupLocations Add a spec descriptor for configuration Add a spec descriptor for snapshotLocations Warning: Value oadp.openshift.io/v1alpha1, Kind=CloudStorage: provided API should have an example annotation Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotBackup: provided API should have an example annotation Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotRestore: provided API should have an example annotation	CHECK THE WARNINGS (+) For oadp-operator.v1.0.4: Warning: Value oadp-operator.v1.0.4: owned CRD "cloudstorages.oadp.openshift.io" has an empty description Warning: Value : (oadp-operator.v1.0.4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value oadp.openshift.io/v1alpha1, Kind=CloudStorage: provided API should have an example annotation For oadp-operator.v1.1.0: Warning: Value oadp-operator.v1.1.0: owned CRD "cloudstorages.oadp.openshift.io" has an empty description Warning: Value oadp-operator.v1.1.0: owned CRD "volumesnapshotbackups.datamover.oadp.openshift.io" has an empty description Warning: Value oadp-operator.v1.1.0: owned CRD "volumesnapshotrestores.datamover.oadp.openshift.io" has an empty description Warning: Value : (oadp-operator.v1.1.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotBackup: provided API should have an example annotation Warning: Value oadp.openshift.io/v1alpha1, Kind=CloudStorage: provided API should have an example annotation Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotRestore: provided API should have an example annotation For oadp-operator.v1.1.0: Warning: Value oadp-operator.v1.1.0: owned CRD "cloudstorages.oadp.openshift.io" has an empty description Warning: Value oadp-operator.v1.1.0: owned CRD "volumesnapshotbackups.datamover.oadp.openshift.io" has an empty description Warning: Value oadp-operator.v1.1.0: owned CRD "volumesnapshotrestores.datamover.oadp.openshift.io" has an empty description Warning: Value : (oadp-operator.v1.1.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotBackup: provided API should have an example annotation Warning: Value oadp.openshift.io/v1alpha1, Kind=CloudStorage: provided API should have an example annotation Warning: Value datamover.oadp.openshift.io/v1alpha1, Kind=VolumeSnapshotRestore: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
3scale-operator	NOT COMPLY Following those does NOT complies: (+) . threescale-2.12 threescale-2.11 threescale-mas	USED	FIX ERRORS AND WARNINGS (+) For 3scale-operator.v0.8.4: Owned CRDs do not have resources specified backupDestination does not have a spec descriptor restoreSource does not have a spec descriptor systemMasterUrl does not have a spec descriptor tenantSecretRef does not have a spec descriptor username does not have a spec descriptor email does not have a spec descriptor masterCredentialsRef does not have a spec descriptor organizationName does not have a spec descriptor passwordCredentialsRef does not have a spec descriptor activeDocOpenAPIRef does not have a spec descriptor name does not have a spec descriptor name does not have a spec descriptor privateBaseURL does not have a spec descriptor systemName does not have a spec descriptor name does not have a spec descriptor schema does not have a spec descriptor version does not have a spec descriptor orgName does not have a spec descriptor passwordCredentialsRef does not have a spec descriptor role does not have a spec descriptor username does not have a spec descriptor developerAccountRef does not have a spec descriptor email does not have a spec descriptor openapiRef does not have a spec descriptor name does not have a spec descriptor Add a spec descriptor for backupDestination Add a spec descriptor for restoreSource Add a spec descriptor for systemMasterUrl Add a spec descriptor for tenantSecretRef Add a spec descriptor for username Add a spec descriptor for email Add a spec descriptor for masterCredentialsRef Add a spec descriptor for organizationName Add a spec descriptor for passwordCredentialsRef Add a spec descriptor for activeDocOpenAPIRef Add a spec descriptor for name Add a spec descriptor for name Add a spec descriptor for privateBaseURL Add a spec descriptor for systemName Add a spec descriptor for name Add a spec descriptor for schema Add a spec descriptor for version Add a spec descriptor for orgName Add a spec descriptor for passwordCredentialsRef Add a spec descriptor for role Add a spec descriptor for username Add a spec descriptor for developerAccountRef Add a spec descriptor for email Add a spec descriptor for openapiRef Add a spec descriptor for name apimanagers.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apimanagerbackups.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apimanagerrestores.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tenants.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status activedocs.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backends.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status custompolicydefinitions.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status developeraccounts.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status developerusers.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status openapis.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status products.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For 3scale-operator.v0.9.0-mas: backupDestination does not have a spec descriptor restoreSource does not have a spec descriptor systemMasterUrl does not have a spec descriptor tenantSecretRef does not have a spec descriptor username does not have a spec descriptor email does not have a spec descriptor masterCredentialsRef does not have a spec descriptor organizationName does not have a spec descriptor passwordCredentialsRef does not have a spec descriptor activeDocOpenAPIRef does not have a spec descriptor name does not have a spec descriptor name does not have a spec descriptor privateBaseURL does not have a spec descriptor systemName does not have a spec descriptor version does not have a spec descriptor name does not have a spec descriptor schema does not have a spec descriptor orgName does not have a spec descriptor developerAccountRef does not have a spec descriptor email does not have a spec descriptor passwordCredentialsRef does not have a spec descriptor role does not have a spec descriptor username does not have a spec descriptor openapiRef does not have a spec descriptor name does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for backupDestination Add a spec descriptor for restoreSource Add a spec descriptor for systemMasterUrl Add a spec descriptor for tenantSecretRef Add a spec descriptor for username Add a spec descriptor for email Add a spec descriptor for masterCredentialsRef Add a spec descriptor for organizationName Add a spec descriptor for passwordCredentialsRef Add a spec descriptor for activeDocOpenAPIRef Add a spec descriptor for name Add a spec descriptor for name Add a spec descriptor for privateBaseURL Add a spec descriptor for systemName Add a spec descriptor for version Add a spec descriptor for name Add a spec descriptor for schema Add a spec descriptor for orgName Add a spec descriptor for developerAccountRef Add a spec descriptor for email Add a spec descriptor for passwordCredentialsRef Add a spec descriptor for role Add a spec descriptor for username Add a spec descriptor for openapiRef Add a spec descriptor for name apimanagers.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apimanagerbackups.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apimanagerrestores.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tenants.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status activedocs.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backends.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status custompolicydefinitions.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status developeraccounts.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status developerusers.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status openapis.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status products.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For 3scale-operator.v0.9.1: backupDestination does not have a spec descriptor restoreSource does not have a spec descriptor email does not have a spec descriptor masterCredentialsRef does not have a spec descriptor organizationName does not have a spec descriptor passwordCredentialsRef does not have a spec descriptor systemMasterUrl does not have a spec descriptor tenantSecretRef does not have a spec descriptor username does not have a spec descriptor activeDocOpenAPIRef does not have a spec descriptor name does not have a spec descriptor systemName does not have a spec descriptor name does not have a spec descriptor privateBaseURL does not have a spec descriptor schema does not have a spec descriptor version does not have a spec descriptor name does not have a spec descriptor orgName does not have a spec descriptor username does not have a spec descriptor developerAccountRef does not have a spec descriptor email does not have a spec descriptor passwordCredentialsRef does not have a spec descriptor role does not have a spec descriptor openapiRef does not have a spec descriptor name does not have a spec descriptor Owned CRDs do not have resources specified apimanagers.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apimanagerbackups.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status apimanagerrestores.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tenants.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status activedocs.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backends.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status custompolicydefinitions.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status developeraccounts.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status developerusers.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status openapis.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status products.capabilities.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for backupDestination Add a spec descriptor for restoreSource Add a spec descriptor for email Add a spec descriptor for masterCredentialsRef Add a spec descriptor for organizationName Add a spec descriptor for passwordCredentialsRef Add a spec descriptor for systemMasterUrl Add a spec descriptor for tenantSecretRef Add a spec descriptor for username Add a spec descriptor for activeDocOpenAPIRef Add a spec descriptor for name Add a spec descriptor for systemName Add a spec descriptor for name Add a spec descriptor for privateBaseURL Add a spec descriptor for schema Add a spec descriptor for version Add a spec descriptor for name Add a spec descriptor for orgName Add a spec descriptor for username Add a spec descriptor for developerAccountRef Add a spec descriptor for email Add a spec descriptor for passwordCredentialsRef Add a spec descriptor for role Add a spec descriptor for openapiRef Add a spec descriptor for name	CHECK THE WARNINGS (+) For 3scale-operator.v0.8.4: Warning: Value 3scale-operator.v0.8.4: channel(s) ["threescale-2.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (3scale-operator.v0.8.4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For 3scale-operator.v0.9.0-mas: Warning: Value 3scale-operator.v0.9.0-mas: channel(s) ["threescale-mas"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (3scale-operator.v0.9.0-mas) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For 3scale-operator.v0.9.1: Warning: Value 3scale-operator.v0.9.1: channel(s) ["threescale-2.12"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (3scale-operator.v0.9.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Deep Insights]	"Red Hat Integration" "Red Hat 3scale API Management"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
apicast-operator	NOT COMPLY Following those does NOT complies: (+) . threescale-2.11 threescale-2.12 threescale-mas	USED	FIX ERRORS AND WARNINGS (+) For apicast-operator.v0.5.3: Owned CRDs do not have resources specified adminPortalCredentialsRef does not have a spec descriptor apicasts.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for adminPortalCredentialsRef For apicast-operator.v0.6.1: Owned CRDs do not have resources specified adminPortalCredentialsRef does not have a spec descriptor apicasts.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for adminPortalCredentialsRef For apicast-operator.v0.6.0-mas: Owned CRDs do not have resources specified adminPortalCredentialsRef does not have a spec descriptor apicasts.apps.3scale.net does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for adminPortalCredentialsRef	CHECK THE WARNINGS (+) For apicast-operator.v0.5.3: Warning: Value apicast-operator.v0.5.3: channel(s) ["threescale-2.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For apicast-operator.v0.6.1: Warning: Value apicast-operator.v0.6.1: channel(s) ["threescale-2.12"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For apicast-operator.v0.6.0-mas: Warning: Value apicast-operator.v0.6.0-mas: channel(s) ["threescale-mas"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Full Lifecycle]	"Red Hat Integration" "Red Hat 3scale API Management"		USED	NOT USED
costmanagement-metrics-operator	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For costmanagement-metrics-operator.1.1.7: Owned CRDs do not have resources specified authentication does not have a spec descriptor packaging does not have a spec descriptor prometheus_config does not have a spec descriptor source does not have a spec descriptor upload does not have a spec descriptor costmanagementmetricsconfigs.costmanagement-metrics-cfg.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for authentication Add a spec descriptor for packaging Add a spec descriptor for prometheus_config Add a spec descriptor for source Add a spec descriptor for upload	CHECK THE WARNINGS (+) For costmanagement-metrics-operator.1.1.7: Warning: Value costmanagement-metrics-operator.1.1.7: csv.metadata.Name costmanagement-metrics-operator.1.1.7 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (costmanagement-metrics-operator.1.1.7) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
devworkspace-operator	PROBABLY COMPLY Following those complies: fast	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For devworkspace-operator.v0.15.2-0.1661828401.p: Owned CRDs do not have resources specified Warning: Value workspace.devfile.io/v1alpha2, Kind=DevWorkspace: provided API should have an example annotation Warning: Value workspace.devfile.io/v1alpha1, Kind=DevWorkspaceTemplate: provided API should have an example annotation Warning: Value workspace.devfile.io/v1alpha2, Kind=DevWorkspaceTemplate: provided API should have an example annotation Warning: Value controller.devfile.io/v1alpha1, Kind=DevWorkspaceOperatorConfig: provided API should have an example annotation Warning: Value controller.devfile.io/v1alpha1, Kind=DevWorkspaceRouting: provided API should have an example annotation Warning: Value workspace.devfile.io/v1alpha1, Kind=DevWorkspace: provided API should have an example annotation	CHECK THE WARNINGS (+) For devworkspace-operator.v0.15.2-0.1661828401.p: Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: owned CRD "devworkspaceoperatorconfigs.controller.devfile.io" has an empty description Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: owned CRD "devworkspaceroutings.controller.devfile.io" has an empty description Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: owned CRD "devworkspaces.workspace.devfile.io" has an empty description Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: owned CRD "devworkspaces.workspace.devfile.io" has an empty description Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: owned CRD "devworkspacetemplates.workspace.devfile.io" has an empty description Warning: Value devworkspace-operator.v0.15.2-0.1661828401.p: owned CRD "devworkspacetemplates.workspace.devfile.io" has an empty description Warning: Value : (devworkspace-operator.v0.15.2-0.1661828401.p) csv.Spec.Icon not specified Warning: Value : (devworkspace-operator.v0.15.2-0.1661828401.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value workspace.devfile.io/v1alpha1, Kind=DevWorkspace: provided API should have an example annotation Warning: Value workspace.devfile.io/v1alpha2, Kind=DevWorkspace: provided API should have an example annotation Warning: Value workspace.devfile.io/v1alpha1, Kind=DevWorkspaceTemplate: provided API should have an example annotation Warning: Value workspace.devfile.io/v1alpha2, Kind=DevWorkspaceTemplate: provided API should have an example annotation Warning: Value controller.devfile.io/v1alpha1, Kind=DevWorkspaceOperatorConfig: provided API should have an example annotation Warning: Value controller.devfile.io/v1alpha1, Kind=DevWorkspaceRouting: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
gatekeeper-operator-product	PROBABLY COMPLY Following those complies: stable	USED	CHECK THE WARNINGS (+) For gatekeeper-operator-product.v0.2.4: gatekeepers.operator.gatekeeper.sh does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For gatekeeper-operator-product.v0.2.4: Warning: Value gatekeeper-operator-product.v0.2.4: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value gatekeeper-operator-product.v0.2.4: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (gatekeeper-operator-product.v0.2.4) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Platform Plus" "Red Hat Advanced Cluster Management for Kubernetes"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (apiGroups/resources): policy/podsecuritypolicies (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
self-node-remediation	PROBABLY COMPLY Following those complies: stable	USED	CHECK THE WARNINGS (+) For self-node-remediation.v0.4.1: selfnoderemediations.self-node-remediation.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status selfnoderemediationconfigs.self-node-remediation.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status selfnoderemediationtemplates.self-node-remediation.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	PASSED IN ALL CHECKS	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
cluster-logging	PROBABLY COMPLY Following those complies: stable-5.2 stable-5.3 stable-5.4 stable stable-5.5	USED	FIX ERRORS AND WARNINGS (+) For cluster-logging.5.2.12: managementState does not have a spec descriptor logStore does not have a spec descriptor visualization does not have a spec descriptor collection does not have a spec descriptor outputs does not have a spec descriptor pipelines does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for managementState Add a spec descriptor for logStore Add a spec descriptor for visualization Add a spec descriptor for collection Add a spec descriptor for outputs Add a spec descriptor for pipelines clusterloggings.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status clusterlogforwarders.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For cluster-logging.5.3.9: logStore does not have a spec descriptor visualization does not have a spec descriptor collection does not have a spec descriptor managementState does not have a spec descriptor outputs does not have a spec descriptor pipelines does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for logStore Add a spec descriptor for visualization Add a spec descriptor for collection Add a spec descriptor for managementState Add a spec descriptor for outputs Add a spec descriptor for pipelines clusterloggings.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status clusterlogforwarders.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For cluster-logging.5.4.5: managementState does not have a spec descriptor logStore does not have a spec descriptor visualization does not have a spec descriptor collection does not have a spec descriptor outputs does not have a spec descriptor pipelines does not have a spec descriptor Owned CRDs do not have resources specified clusterloggings.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status clusterlogforwarders.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for managementState Add a spec descriptor for logStore Add a spec descriptor for visualization Add a spec descriptor for collection Add a spec descriptor for outputs Add a spec descriptor for pipelines For cluster-logging.5.5.1: visualization does not have a spec descriptor collection does not have a spec descriptor logStore does not have a spec descriptor managementState does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for visualization Add a spec descriptor for collection Add a spec descriptor for logStore Add a spec descriptor for managementState clusterlogforwarders.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status clusterloggings.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For cluster-logging.5.5.1: visualization does not have a spec descriptor collection does not have a spec descriptor logStore does not have a spec descriptor managementState does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for visualization Add a spec descriptor for collection Add a spec descriptor for logStore Add a spec descriptor for managementState clusterlogforwarders.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status clusterloggings.logging.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For cluster-logging.5.2.12: Warning: Value cluster-logging.5.2.12: unable to find the resource requests for the container: (cluster-logging-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value cluster-logging.5.2.12: csv.metadata.Name cluster-logging.5.2.12 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For cluster-logging.5.3.9: Warning: Value cluster-logging.5.3.9: unable to find the resource requests for the container: (cluster-logging-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value cluster-logging.5.3.9: csv.metadata.Name cluster-logging.5.3.9 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For cluster-logging.5.4.5: Warning: Value cluster-logging.5.4.5: unable to find the resource requests for the container: (cluster-logging-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value cluster-logging.5.4.5: csv.metadata.Name cluster-logging.5.4.5 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For cluster-logging.5.5.1: Warning: Value cluster-logging.5.5.1: unable to find the resource requests for the container: (cluster-logging-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value cluster-logging.5.5.1: csv.metadata.Name cluster-logging.5.5.1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 For cluster-logging.5.5.1: Warning: Value cluster-logging.5.5.1: unable to find the resource requests for the container: (cluster-logging-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value cluster-logging.5.5.1: csv.metadata.Name cluster-logging.5.5.1 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
clusterresourceoverride	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For clusterresourceoverride-operator.4.11.0-202208291725: podResourceOverride does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for podResourceOverride clusterresourceoverrides.operator.autoscaling.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For clusterresourceoverride-operator.4.11.0-202208291725: podResourceOverride does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for podResourceOverride clusterresourceoverrides.operator.autoscaling.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For clusterresourceoverride-operator.4.11.0-202208291725: Warning: Value clusterresourceoverride-operator.4.11.0-202208291725: unable to find the resource requests for the container: (clusterresourceoverride-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value clusterresourceoverride-operator.4.11.0-202208291725: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value clusterresourceoverride-operator.4.11.0-202208291725: csv.metadata.Name clusterresourceoverride-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (clusterresourceoverride-operator.4.11.0-202208291725) csv.Spec.Icon not specified Warning: Value : (clusterresourceoverride-operator.4.11.0-202208291725) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For clusterresourceoverride-operator.4.11.0-202208291725: Warning: Value clusterresourceoverride-operator.4.11.0-202208291725: unable to find the resource requests for the container: (clusterresourceoverride-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value clusterresourceoverride-operator.4.11.0-202208291725: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value clusterresourceoverride-operator.4.11.0-202208291725: csv.metadata.Name clusterresourceoverride-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (clusterresourceoverride-operator.4.11.0-202208291725) csv.Spec.Icon not specified Warning: Value : (clusterresourceoverride-operator.4.11.0-202208291725) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): flowcontrol.apiserver.k8s.io/flowschemas (apiGroups/resources): flowcontrol.apiserver.k8s.io/prioritylevelconfigurations (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
node-healthcheck-operator	NOT COMPLY Following those does NOT complies: (+) . alpha Following those complies: candidate stable	SHOULD SUPPORT	CHECK THE WARNINGS (+) For node-healthcheck-operator.v0.1.0: nodehealthchecks.remediation.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For node-healthcheck-operator.v0.3.1: nodehealthchecks.remediation.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For node-healthcheck-operator.v0.3.1: nodehealthchecks.remediation.medik8s.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For node-healthcheck-operator.v0.1.0: Warning: Value node-healthcheck-operator.v0.1.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value node-healthcheck-operator.v0.1.0: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (node-healthcheck-operator.v0.1.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For node-healthcheck-operator.v0.3.1: Warning: Value node-healthcheck-operator.v0.3.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ For node-healthcheck-operator.v0.3.1: Warning: Value node-healthcheck-operator.v0.3.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
odf-operator	PROBABLY COMPLY Following those complies: stable-4.10 stable-4.11	USED	FIX ERRORS AND WARNINGS (+) For odf-operator.v4.10.5: kind does not have a spec descriptor name does not have a spec descriptor namespace does not have a spec descriptor kind does not have a spec descriptor name does not have a spec descriptor namespace does not have a spec descriptor Add a spec descriptor for kind Add a spec descriptor for name Add a spec descriptor for namespace Add a spec descriptor for kind Add a spec descriptor for name Add a spec descriptor for namespace storagesystems.odf.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status storagesystems.odf.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For odf-operator.v4.11.1: kind does not have a spec descriptor name does not have a spec descriptor namespace does not have a spec descriptor kind does not have a spec descriptor name does not have a spec descriptor namespace does not have a spec descriptor Add a spec descriptor for kind Add a spec descriptor for name Add a spec descriptor for namespace Add a spec descriptor for kind Add a spec descriptor for name Add a spec descriptor for namespace storagesystems.odf.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status storagesystems.odf.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For odf-operator.v4.10.5: Warning: Value odf-operator.v4.10.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-operator.v4.10.5: unable to find the resource requests for the container: (odf-console). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-operator.v4.10.5: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (odf-operator.v4.10.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For odf-operator.v4.11.1: Warning: Value odf-operator.v4.11.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-operator.v4.11.1: unable to find the resource requests for the container: (odf-console). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-operator.v4.11.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (odf-operator.v4.11.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Deep Insights]	"OpenShift Platform Plus" "OpenShift Data Foundation Essentials" "OpenShift Data Foundation Advanced"		USED	NOT USED
openshift-gitops-operator	NOT COMPLY Following those does NOT complies: (+) . latest gitops-1.6 gitops-1.5 gitops-1.3 gitops-1.4 preview Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For openshift-gitops-operator.v1.6.1: error spec does not exist for the custom resource example resourceExclusions does not have a spec descriptor server does not have a spec descriptor sso does not have a spec descriptor controller does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor redis does not have a spec descriptor repo does not have a spec descriptor Owned CRDs do not have resources specified appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example] Add a spec descriptor for resourceExclusions Add a spec descriptor for server Add a spec descriptor for sso Add a spec descriptor for controller Add a spec descriptor for ha Add a spec descriptor for rbac Add a spec descriptor for redis Add a spec descriptor for repo For openshift-gitops-operator.v1.6.1: error spec does not exist for the custom resource example resourceExclusions does not have a spec descriptor server does not have a spec descriptor sso does not have a spec descriptor controller does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor redis does not have a spec descriptor repo does not have a spec descriptor Owned CRDs do not have resources specified appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example] Add a spec descriptor for resourceExclusions Add a spec descriptor for server Add a spec descriptor for sso Add a spec descriptor for controller Add a spec descriptor for ha Add a spec descriptor for rbac Add a spec descriptor for redis Add a spec descriptor for repo For openshift-gitops-operator.v1.5.6: redis does not have a spec descriptor repo does not have a spec descriptor server does not have a spec descriptor controller does not have a spec descriptor dex does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor Owned CRDs do not have resources specified error spec does not exist for the custom resource example Add a spec descriptor for redis Add a spec descriptor for repo Add a spec descriptor for server Add a spec descriptor for controller Add a spec descriptor for dex Add a spec descriptor for ha Add a spec descriptor for rbac appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example] For openshift-gitops-operator.v1.5.6: redis does not have a spec descriptor repo does not have a spec descriptor server does not have a spec descriptor controller does not have a spec descriptor dex does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor Owned CRDs do not have resources specified error spec does not exist for the custom resource example Add a spec descriptor for redis Add a spec descriptor for repo Add a spec descriptor for server Add a spec descriptor for controller Add a spec descriptor for dex Add a spec descriptor for ha Add a spec descriptor for rbac appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example] For openshift-gitops-operator.v1.3.13: error spec does not exist for the custom resource example dex does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor redis does not have a spec descriptor repo does not have a spec descriptor server does not have a spec descriptor controller does not have a spec descriptor Owned CRDs do not have resources specified spec missing from [example] Add a spec descriptor for dex Add a spec descriptor for ha Add a spec descriptor for rbac Add a spec descriptor for redis Add a spec descriptor for repo Add a spec descriptor for server Add a spec descriptor for controller appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For openshift-gitops-operator.v1.4.12: dex does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor redis does not have a spec descriptor repo does not have a spec descriptor server does not have a spec descriptor controller does not have a spec descriptor Owned CRDs do not have resources specified error spec does not exist for the custom resource example Add a spec descriptor for dex Add a spec descriptor for ha Add a spec descriptor for rbac Add a spec descriptor for redis Add a spec descriptor for repo Add a spec descriptor for server Add a spec descriptor for controller appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status spec missing from [example] For openshift-gitops-operator.v1.4.8: Owned CRDs do not have resources specified dex does not have a spec descriptor ha does not have a spec descriptor rbac does not have a spec descriptor redis does not have a spec descriptor repo does not have a spec descriptor server does not have a spec descriptor controller does not have a spec descriptor error spec does not exist for the custom resource example Add a spec descriptor for dex Add a spec descriptor for ha Add a spec descriptor for rbac Add a spec descriptor for redis Add a spec descriptor for repo Add a spec descriptor for server Add a spec descriptor for controller spec missing from [example] appprojects.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applications.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status applicationsets.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status argocds.argoproj.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status gitopsservices.pipelines.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For openshift-gitops-operator.v1.6.1: Warning: Value openshift-gitops-operator.v1.6.1: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.6.1: channel(s) ["gitops-1.6" "latest"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.6.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-gitops-operator.v1.6.1: Warning: Value openshift-gitops-operator.v1.6.1: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.6.1: channel(s) ["gitops-1.6" "latest"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.6.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-gitops-operator.v1.5.6: Warning: Value openshift-gitops-operator.v1.5.6: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.5.6: channel(s) ["gitops-1.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.5.6) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-gitops-operator.v1.5.6: Warning: Value openshift-gitops-operator.v1.5.6: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.5.6: channel(s) ["gitops-1.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.5.6) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-gitops-operator.v1.3.13: Warning: Value openshift-gitops-operator.v1.3.13: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.3.13: channel(s) ["gitops-1.3"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.3.13) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-gitops-operator.v1.4.12: Warning: Value openshift-gitops-operator.v1.4.12: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.4.12: channel(s) ["gitops-1.4"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.4.12) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For openshift-gitops-operator.v1.4.8: Warning: Value openshift-gitops-operator.v1.4.8: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-gitops-operator.v1.4.8: channel(s) ["gitops-1.4" "preview"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (openshift-gitops-operator.v1.4.8) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Deep Insights]	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (apiGroups/resources): autoscaling/horizontalpodautoscalers (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
openshift-special-resource-operator	NOT COMPLY Following those does NOT complies: (+) . 4.11 Following those complies: stable	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. openshift-special-resource-operator.4.11.0-202208291725 openshift-special-resource-operator.4.11.0-202208291725	FIX ERRORS AND WARNINGS (+) For openshift-special-resource-operator.4.11.0-202208291725: chart does not have a spec descriptor driverContainer does not have a spec descriptor namespace does not have a spec descriptor set does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for chart Add a spec descriptor for driverContainer Add a spec descriptor for namespace Add a spec descriptor for set Warning: Value sro.openshift.io/v1beta1, Kind=PreflightValidation: provided API should have an example annotation Warning: Value sro.openshift.io/v1beta1, Kind=SpecialResourceModule: provided API should have an example annotation specialresources.sro.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For openshift-special-resource-operator.4.11.0-202208291725: chart does not have a spec descriptor driverContainer does not have a spec descriptor namespace does not have a spec descriptor set does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for chart Add a spec descriptor for driverContainer Add a spec descriptor for namespace Add a spec descriptor for set Warning: Value sro.openshift.io/v1beta1, Kind=PreflightValidation: provided API should have an example annotation Warning: Value sro.openshift.io/v1beta1, Kind=SpecialResourceModule: provided API should have an example annotation specialresources.sro.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For openshift-special-resource-operator.4.11.0-202208291725: Warning: Value openshift-special-resource-operator.4.11.0-202208291725: owned CRD "preflightvalidations.sro.openshift.io" has an empty description Warning: Value openshift-special-resource-operator.4.11.0-202208291725: owned CRD "specialresourcemodules.sro.openshift.io" has an empty description Warning: Value openshift-special-resource-operator.4.11.0-202208291725: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value openshift-special-resource-operator.4.11.0-202208291725: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value openshift-special-resource-operator.4.11.0-202208291725: csv.metadata.Name openshift-special-resource-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (openshift-special-resource-operator.4.11.0-202208291725) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value sro.openshift.io/v1beta1, Kind=PreflightValidation: provided API should have an example annotation Warning: Value sro.openshift.io/v1beta1, Kind=SpecialResourceModule: provided API should have an example annotation For openshift-special-resource-operator.4.11.0-202208291725: Warning: Value openshift-special-resource-operator.4.11.0-202208291725: owned CRD "preflightvalidations.sro.openshift.io" has an empty description Warning: Value openshift-special-resource-operator.4.11.0-202208291725: owned CRD "specialresourcemodules.sro.openshift.io" has an empty description Warning: Value openshift-special-resource-operator.4.11.0-202208291725: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value openshift-special-resource-operator.4.11.0-202208291725: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value openshift-special-resource-operator.4.11.0-202208291725: csv.metadata.Name openshift-special-resource-operator.4.11.0-202208291725 is not following the recommended naming convention: <operator-name>.v<semver> e.g. memcached-operator.v0.0.1 Warning: Value : (openshift-special-resource-operator.4.11.0-202208291725) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value sro.openshift.io/v1beta1, Kind=PreflightValidation: provided API should have an example annotation Warning: Value sro.openshift.io/v1beta1, Kind=SpecialResourceModule: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
serverless-operator	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For serverless-operator.v1.24.0: channel does not have a spec descriptor broker does not have a spec descriptor source does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for channel Add a spec descriptor for broker Add a spec descriptor for source knativeservings.operator.knative.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status knativeeventings.operator.knative.dev does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status knativekafkas.operator.serverless.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For serverless-operator.v1.24.0: Warning: Value serverless-operator.v1.24.0: unable to find the resource requests for the container: (knative-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value serverless-operator.v1.24.0: unable to find the resource requests for the container: (knative-openshift). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value serverless-operator.v1.24.0: unable to find the resource requests for the container: (knative-openshift-ingress). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value serverless-operator.v1.24.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/	[Full Lifecycle]	"OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (apiGroups/resources): autoscaling/horizontalpodautoscalers (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
submariner	NOT COMPLY Following those does NOT complies: (+) . alpha-0.11 alpha-0.9 Following those complies: stable-0.13 stable-0.12	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For submariner.v0.11.2: brokers.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status submariners.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For submariner.v0.13.0: brokers.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status submariners.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For submariner.v0.9.0: components does not have a spec descriptor defaultGlobalnetClusterSize does not have a spec descriptor globalnetEnabled does not have a spec descriptor brokerK8sApiServer does not have a spec descriptor brokerK8sCA does not have a spec descriptor cableDriver does not have a spec descriptor clusterID does not have a spec descriptor namespace does not have a spec descriptor brokerK8sApiServerToken does not have a spec descriptor clusterCIDR does not have a spec descriptor serviceCIDR does not have a spec descriptor broker does not have a spec descriptor brokerK8sRemoteNamespace does not have a spec descriptor ceIPSecDebug does not have a spec descriptor ceIPSecPSK does not have a spec descriptor debug does not have a spec descriptor globalCIDR does not have a spec descriptor version does not have a spec descriptor ceIPSecIKEPort does not have a spec descriptor ceIPSecNATTPort does not have a spec descriptor connectionHealthCheck does not have a spec descriptor natEnabled does not have a spec descriptor repository does not have a spec descriptor serviceDiscoveryEnabled does not have a spec descriptor Error: Value submariner-operator: invalid service account found in bundle. This service account submariner-operator in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Owned CRDs do not have resources specified Add a spec descriptor for components Add a spec descriptor for defaultGlobalnetClusterSize Add a spec descriptor for globalnetEnabled Add a spec descriptor for brokerK8sApiServer Add a spec descriptor for brokerK8sCA Add a spec descriptor for cableDriver Add a spec descriptor for clusterID Add a spec descriptor for namespace Add a spec descriptor for brokerK8sApiServerToken Add a spec descriptor for clusterCIDR Add a spec descriptor for serviceCIDR Add a spec descriptor for broker Add a spec descriptor for brokerK8sRemoteNamespace Add a spec descriptor for ceIPSecDebug Add a spec descriptor for ceIPSecPSK Add a spec descriptor for debug Add a spec descriptor for globalCIDR Add a spec descriptor for version Add a spec descriptor for ceIPSecIKEPort Add a spec descriptor for ceIPSecNATTPort Add a spec descriptor for connectionHealthCheck Add a spec descriptor for natEnabled Add a spec descriptor for repository Add a spec descriptor for serviceDiscoveryEnabled brokers.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status submariners.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For submariner.v0.12.2: brokers.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status submariners.submariner.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	FIX ERRORS AND WARNINGS (+) For submariner.v0.11.2: Warning: Value submariner.v0.11.2: unable to find the resource requests for the container: (submariner-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value submariner.v0.11.2: channel(s) ["alpha-0.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value submariner.v0.11.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (submariner.v0.11.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For submariner.v0.13.0: Warning: Value submariner.v0.13.0: unable to find the resource requests for the container: (submariner-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value submariner.v0.13.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (submariner.v0.13.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For submariner.v0.9.0: Error: Value submariner-operator: invalid service account found in bundle. This service account submariner-operator in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Warning: Value submariner.v0.9.0: unable to find the resource requests for the container: (submariner-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value submariner.v0.9.0: channel(s) ["alpha-0.9"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value submariner.v0.9.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (submariner.v0.9.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For submariner.v0.12.2: Warning: Value submariner.v0.12.2: unable to find the resource requests for the container: (submariner-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value submariner.v0.12.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (submariner.v0.12.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Platform Plus" "Red Hat Advanced Cluster Management for Kubernetes"		USED	NOT USED
compliance-operator	NOT COMPLY Following those does NOT complies: (+) . release-0.1 4.7	USED	FIX ERRORS AND WARNINGS (+) For compliance-operator.v0.1.53: error spec does not exist for the custom resource my-companys-constraints Owned CRDs do not have resources specified content does not have a spec descriptor profile does not have a spec descriptor profile does not have a spec descriptor scanType does not have a spec descriptor content does not have a spec descriptor autoApplyRemediations does not have a spec descriptor scans does not have a spec descriptor schedule does not have a spec descriptor contentFile does not have a spec descriptor contentImage does not have a spec descriptor setValues does not have a spec descriptor title does not have a spec descriptor description does not have a spec descriptor disableRules does not have a spec descriptor extends does not have a spec descriptor spec missing from [my-companys-constraints] compliancescans.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status compliancescans.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status compliancesuites.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status profilebundles.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status scansettings.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status scansettingbindings.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tailoredprofiles.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value compliance.openshift.io/v1alpha1, Kind=Rule: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceRemediation: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Profile: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Variable: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceCheckResult: provided API should have an example annotation Add a spec descriptor for content Add a spec descriptor for profile Add a spec descriptor for profile Add a spec descriptor for scanType Add a spec descriptor for content Add a spec descriptor for autoApplyRemediations Add a spec descriptor for scans Add a spec descriptor for schedule Add a spec descriptor for contentFile Add a spec descriptor for contentImage Add a spec descriptor for setValues Add a spec descriptor for title Add a spec descriptor for description Add a spec descriptor for disableRules Add a spec descriptor for extends For compliance-operator.v0.1.32: Owned CRDs do not have resources specified error spec does not exist for the custom resource my-companys-constraints content does not have a spec descriptor profile does not have a spec descriptor content does not have a spec descriptor profile does not have a spec descriptor scanType does not have a spec descriptor autoApplyRemediations does not have a spec descriptor scans does not have a spec descriptor schedule does not have a spec descriptor contentFile does not have a spec descriptor contentImage does not have a spec descriptor disableRules does not have a spec descriptor extends does not have a spec descriptor setValues does not have a spec descriptor title does not have a spec descriptor spec missing from [my-companys-constraints] Warning: Value compliance.openshift.io/v1alpha1, Kind=Profile: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceRemediation: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Rule: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Variable: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceCheckResult: provided API should have an example annotation compliancescans.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status compliancescans.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status compliancesuites.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status profilebundles.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status scansettings.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status scansettingbindings.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tailoredprofiles.compliance.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for content Add a spec descriptor for profile Add a spec descriptor for content Add a spec descriptor for profile Add a spec descriptor for scanType Add a spec descriptor for autoApplyRemediations Add a spec descriptor for scans Add a spec descriptor for schedule Add a spec descriptor for contentFile Add a spec descriptor for contentImage Add a spec descriptor for disableRules Add a spec descriptor for extends Add a spec descriptor for setValues Add a spec descriptor for title	CHECK THE WARNINGS (+) For compliance-operator.v0.1.53: Warning: Value compliance-operator.v0.1.53: channel(s) ["release-0.1"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (compliance-operator.v0.1.53) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value compliance.openshift.io/v1alpha1, Kind=Profile: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Rule: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Variable: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceCheckResult: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceRemediation: provided API should have an example annotation For compliance-operator.v0.1.32: Warning: Value compliance-operator.v0.1.32: channel(s) ["4.7"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (compliance-operator.v0.1.32) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value compliance.openshift.io/v1alpha1, Kind=Variable: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Profile: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=Rule: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceCheckResult: provided API should have an example annotation Warning: Value compliance.openshift.io/v1alpha1, Kind=ComplianceRemediation: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (apiGroups/resources): node.k8s.io/runtimeclasses (apiGroups/resources): events.k8s.io/events (apiGroups/resources): autoscaling/horizontalpodautoscalers (apiGroups/resources): policy/podsecuritypolicies (apiGroups/resources): policy/poddisruptionbudgets (apiGroups/resources): flowcontrol.apiserver.k8s.io/flowschemas (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
datagrid	NOT COMPLY Following those does NOT complies: (+) . 8.3.x 8.2.x	USED	FIX ERRORS AND WARNINGS (+) For datagrid-operator.v8.3.7: container does not have a spec descriptor name does not have a spec descriptor templateName does not have a spec descriptor container does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for container Add a spec descriptor for name Add a spec descriptor for templateName Add a spec descriptor for container infinispans.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backups.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status batches.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status caches.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status restores.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For datagrid-operator.v8.2.8: Owned CRDs do not have resources specified container does not have a spec descriptor name does not have a spec descriptor adminAuth does not have a spec descriptor container does not have a spec descriptor Add a spec descriptor for container Add a spec descriptor for name Add a spec descriptor for adminAuth Add a spec descriptor for container infinispans.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status backups.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status caches.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status restores.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status batches.infinispan.org does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For datagrid-operator.v8.3.7: Warning: Value datagrid-operator.v8.3.7: unable to find the resource requests for the container: (manager). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value datagrid-operator.v8.3.7: channel(s) ["8.3.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For datagrid-operator.v8.2.8: Warning: Value datagrid-operator.v8.2.8: unable to find the resource requests for the container: (infinispan-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value datagrid-operator.v8.2.8: channel(s) ["8.2.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Deep Insights]	"Red Hat Data Grid" "Red Hat Runtimes" "Red Hat Integration" "Red Hat Process Automation"	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
kubevirt-hyperconverged	PROBABLY COMPLY Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For kubevirt-hyperconverged-operator.v4.11.0: multus does not have a spec descriptor ovs does not have a spec descriptor imagePullPolicy does not have a spec descriptor kubeMacPool does not have a spec descriptor linuxBridge does not have a spec descriptor macvtap does not have a spec descriptor imagePullPolicy does not have a spec descriptor templateValidator does not have a spec descriptor commonTemplates does not have a spec descriptor featureGates does not have a spec descriptor pipelines does not have a spec descriptor imagePullPolicy does not have a spec descriptor imagePullPolicy does not have a spec descriptor storagePools does not have a spec descriptor workload does not have a spec descriptor Owned CRDs do not have resources specified hyperconvergeds.hco.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status networkaddonsconfigs.networkaddonsoperator.network.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kubevirts.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status ssps.ssp.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status tektontasks.tektontasks.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status cdis.cdi.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status hostpathprovisioners.hostpathprovisioner.kubevirt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for multus Add a spec descriptor for ovs Add a spec descriptor for imagePullPolicy Add a spec descriptor for kubeMacPool Add a spec descriptor for linuxBridge Add a spec descriptor for macvtap Add a spec descriptor for imagePullPolicy Add a spec descriptor for templateValidator Add a spec descriptor for commonTemplates Add a spec descriptor for featureGates Add a spec descriptor for pipelines Add a spec descriptor for imagePullPolicy Add a spec descriptor for imagePullPolicy Add a spec descriptor for storagePools Add a spec descriptor for workload	CHECK THE WARNINGS (+) For kubevirt-hyperconverged-operator.v4.11.0: Warning: Value kubevirt-hyperconverged-operator.v4.11.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (kubevirt-hyperconverged-operator.v4.11.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Deep Insights]	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
odf-lvm-operator	PROBABLY COMPLY Following those complies: stable-4.11 stable-4.10	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For odf-lvm-operator.v4.11.1: Owned CRDs do not have resources specified storage does not have a spec descriptor Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroup: provided API should have an example annotation Warning: Value topolvm.cybozu.com/v1, Kind=LogicalVolume: provided API should have an example annotation Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroupNodeStatus: provided API should have an example annotation Add a spec descriptor for storage lvmclusters.lvm.topolvm.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For odf-lvm-operator.v4.10.5: Owned CRDs do not have resources specified storage does not have a spec descriptor lvmclusters.lvm.topolvm.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for storage Warning: Value topolvm.cybozu.com/v1, Kind=LogicalVolume: provided API should have an example annotation Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroupNodeStatus: provided API should have an example annotation Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroup: provided API should have an example annotation	CHECK THE WARNINGS (+) For odf-lvm-operator.v4.11.1: Warning: Value odf-lvm-operator.v4.11.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-lvm-operator.v4.11.1: owned CRD "logicalvolumes.topolvm.cybozu.com" has an empty description Warning: Value odf-lvm-operator.v4.11.1: owned CRD "lvmvolumegroupnodestatuses.lvm.topolvm.io" has an empty description Warning: Value odf-lvm-operator.v4.11.1: owned CRD "lvmvolumegroups.lvm.topolvm.io" has an empty description Warning: Value : (odf-lvm-operator.v4.11.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroupNodeStatus: provided API should have an example annotation Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroup: provided API should have an example annotation Warning: Value topolvm.cybozu.com/v1, Kind=LogicalVolume: provided API should have an example annotation For odf-lvm-operator.v4.10.5: Warning: Value odf-lvm-operator.v4.10.5: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-lvm-operator.v4.10.5: unable to find the resource requests for the container: (metricsexporter). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value odf-lvm-operator.v4.10.5: owned CRD "logicalvolumes.topolvm.cybozu.com" has an empty description Warning: Value odf-lvm-operator.v4.10.5: owned CRD "lvmvolumegroupnodestatuses.lvm.topolvm.io" has an empty description Warning: Value odf-lvm-operator.v4.10.5: owned CRD "lvmvolumegroups.lvm.topolvm.io" has an empty description Warning: Value : (odf-lvm-operator.v4.10.5) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value topolvm.cybozu.com/v1, Kind=LogicalVolume: provided API should have an example annotation Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroupNodeStatus: provided API should have an example annotation Warning: Value lvm.topolvm.io/v1alpha1, Kind=LVMVolumeGroup: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
openshift-cert-manager-operator	NOT COMPLY Following those does NOT complies: (+) . tech-preview	REQUIRED (+) If the package is in Red Hat Operators Supported in Disconnected Mode then must have the annotation. Following the head of the channels without the annotation. openshift-cert-manager.v1.7.1	FIX ERRORS AND WARNINGS (+) For openshift-cert-manager.v1.7.1: Owned CRDs do not have resources specified managementState does not have a spec descriptor certmanagers.operator.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value cert-manager.io/v1, Kind=CertificateRequest: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=Certificate: provided API should have an example annotation Warning: Value acme.cert-manager.io/v1, Kind=Challenge: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=ClusterIssuer: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=Issuer: provided API should have an example annotation Warning: Value acme.cert-manager.io/v1, Kind=Order: provided API should have an example annotation Warning: Value config.openshift.io/v1alpha1, Kind=CertManager: provided API should have an example annotation Add a spec descriptor for managementState Add CRD validation for spec field `managementState` in CertManager/v1alpha1	CHECK THE WARNINGS (+) For openshift-cert-manager.v1.7.1: Warning: Value openshift-cert-manager.v1.7.1: unable to find the resource requests for the container: (cert-manager-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value openshift-cert-manager.v1.7.1: owned CRD "certmanagers.operator.openshift.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "certmanagers.config.openshift.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "certificaterequests.cert-manager.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "certificates.cert-manager.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "challenges.acme.cert-manager.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "clusterissuers.cert-manager.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "issuers.cert-manager.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: owned CRD "orders.acme.cert-manager.io" has an empty description Warning: Value openshift-cert-manager.v1.7.1: channel(s) ["tech-preview"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value openshift-cert-manager.v1.7.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value acme.cert-manager.io/v1, Kind=Challenge: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=ClusterIssuer: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=Issuer: provided API should have an example annotation Warning: Value acme.cert-manager.io/v1, Kind=Order: provided API should have an example annotation Warning: Value config.openshift.io/v1alpha1, Kind=CertManager: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=CertificateRequest: provided API should have an example annotation Warning: Value cert-manager.io/v1, Kind=Certificate: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		NOT USED	NOT USED
numaresources-operator	NOT COMPLY Following those does NOT complies: (+) . 4.11	SHOULD SUPPORT	CHECK THE WARNINGS (+) For numaresources-operator.v4.11.1: Warning: Value nodetopology.openshift.io/v1alpha1, Kind=NUMAResourcesScheduler: provided API should have an example annotation numaresourcesoperators.nodetopology.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For numaresources-operator.v4.11.1: Warning: Value numaresources-operator.v4.11.1: channel(s) ["4.11"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value numaresources-operator.v4.11.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value nodetopology.openshift.io/v1alpha1, Kind=NUMAResourcesScheduler: provided API should have an example annotation	[Basic Install] (+) Check the capabilities doc to know how to improve it.	"OpenShift Kubernetes Engine" "OpenShift Container Platform" "OpenShift Platform Plus"		USED	NOT USED
rhacs-operator	NOT COMPLY Following those does NOT complies: (+) . rhacs-3.71 latest rhacs-3.68 rhacs-3.69 rhacs-3.67 rhacs-3.64 rhacs-3.62 rhacs-3.66 rhacs-3.70 rhacs-3.65	USED	FIX ERRORS AND WARNINGS (+) For rhacs-operator.v3.71.0: centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.68.2: centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.69.2: centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.67.2: centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.64.2: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.62.1: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.66.1: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.70.1: centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.65.1: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For rhacs-operator.v3.71.0: centrals.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status securedclusters.platform.stackrox.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	FIX ERRORS AND WARNINGS (+) For rhacs-operator.v3.71.0: Warning: Value rhacs-operator.v3.71.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.71.0: channel(s) ["latest" "rhacs-3.71"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.68.2: Warning: Value rhacs-operator.v3.68.2: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.68.2: channel(s) ["rhacs-3.68"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.69.2: Warning: Value rhacs-operator.v3.69.2: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.69.2: channel(s) ["rhacs-3.69"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.67.2: Warning: Value rhacs-operator.v3.67.2: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.67.2: channel(s) ["latest" "rhacs-3.67"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.64.2: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Warning: Value rhacs-operator.v3.64.2: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.64.2: channel(s) ["latest" "rhacs-3.64"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.62.1: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Warning: Value rhacs-operator.v3.62.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.62.1: channel(s) ["rhacs-3.62"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.66.1: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Warning: Value rhacs-operator.v3.66.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.66.1: channel(s) ["latest" "rhacs-3.66"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.70.1: Warning: Value rhacs-operator.v3.70.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.70.1: channel(s) ["latest" "rhacs-3.70"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.65.1: Error: Value rhacs-operator-controller-manager: invalid service account found in bundle. This service account rhacs-operator-controller-manager in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV. Warning: Value rhacs-operator.v3.65.1: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.65.1: channel(s) ["latest" "rhacs-3.65"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For rhacs-operator.v3.71.0: Warning: Value rhacs-operator.v3.71.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value rhacs-operator.v3.71.0: channel(s) ["latest" "rhacs-3.71"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
advanced-cluster-management	NOT COMPLY Following those does NOT complies: (+) . release-2.5 release-2.6	USED	FIX ERRORS AND WARNINGS (+) For advanced-cluster-management.v2.5.2: observabilityAddonSpec does not have a spec descriptor storageConfigObject does not have a spec descriptor interval does not have a spec descriptor enableMetrics does not have a spec descriptor storageConfig does not have a spec descriptor observabilityAddonSpec does not have a spec descriptor type does not have a spec descriptor pathname does not have a spec descriptor packageFilter does not have a spec descriptor packageOverrides does not have a spec descriptor placement does not have a spec descriptor Owned CRDs do not have resources specified channels.apps.open-cluster-management.io does not have a status descriptor Add a spec descriptor for observabilityAddonSpec Add a spec descriptor for storageConfigObject Add a spec descriptor for interval Add a spec descriptor for enableMetrics Add a spec descriptor for storageConfig Add a spec descriptor for observabilityAddonSpec Add a spec descriptor for type Add a spec descriptor for pathname Add a spec descriptor for packageFilter Add a spec descriptor for packageOverrides Add a spec descriptor for placement multiclusterhubs.operator.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status multiclusterobservabilities.observability.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status observabilityaddons.observability.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status multiclusterobservabilities.observability.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd channels.apps.open-cluster-management.io. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ subscriptions.apps.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add CRD validation for status field `state` in Channel/v1 Warning: Value apps.open-cluster-management.io/v1, Kind=HelmRelease: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=PlacementRule: provided API should have an example annotation Warning: Value app.k8s.io/v1beta1, Kind=Application: provided API should have an example annotation Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=Deployable: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionStatus: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerDiagnoseConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionReport: provided API should have an example annotation Warning: Value core.observatorium.io/v1alpha1, Kind=Observatorium: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1beta1, Kind=GitOpsCluster: provided API should have an example annotation For advanced-cluster-management.v2.6.1: observabilityAddonSpec does not have a spec descriptor storageConfigObject does not have a spec descriptor interval does not have a spec descriptor enableMetrics does not have a spec descriptor observabilityAddonSpec does not have a spec descriptor storageConfig does not have a spec descriptor type does not have a spec descriptor pathname does not have a spec descriptor packageFilter does not have a spec descriptor packageOverrides does not have a spec descriptor placement does not have a spec descriptor channels.apps.open-cluster-management.io does not have a status descriptor Owned CRDs do not have resources specified Add a spec descriptor for observabilityAddonSpec Add a spec descriptor for storageConfigObject Add a spec descriptor for interval Add a spec descriptor for enableMetrics Add a spec descriptor for observabilityAddonSpec Add a spec descriptor for storageConfig Add a spec descriptor for type Add a spec descriptor for pathname Add a spec descriptor for packageFilter Add a spec descriptor for packageOverrides Add a spec descriptor for placement Add CRD validation for status field `state` in Channel/v1 multiclusterhubs.operator.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status multiclusterobservabilities.observability.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status observabilityaddons.observability.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status multiclusterobservabilities.observability.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status add status descriptor for the crd channels.apps.open-cluster-management.io. If your project is built using Golang you can use the csv markers. More info: https://sdk.operatorframework.io/docs/building-operators/golang/references/markers/ subscriptions.apps.open-cluster-management.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionReport: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=HelmRelease: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1beta1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value app.k8s.io/v1beta1, Kind=Application: provided API should have an example annotation Warning: Value core.observatorium.io/v1alpha1, Kind=Observatorium: provided API should have an example annotation Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerDiagnoseConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=Deployable: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=PlacementRule: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionStatus: provided API should have an example annotation	CHECK THE WARNINGS (+) For advanced-cluster-management.v2.5.2: Warning: Value advanced-cluster-management.v2.5.2: owned CRD "observatoria.core.observatorium.io" has an empty description Warning: Value advanced-cluster-management.v2.5.2: owned CRD "submarinerconfigs.submarineraddon.open-cluster-management.io" has an empty description Warning: Value advanced-cluster-management.v2.5.2: owned CRD "submarinerdiagnoseconfigs.submarineraddon.open-cluster-management.io" has an empty description Warning: Value advanced-cluster-management.v2.5.2: channel(s) ["release-2.5"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value advanced-cluster-management.v2.5.2: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (advanced-cluster-management.v2.5.2) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=PlacementRule: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1beta1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value core.observatorium.io/v1alpha1, Kind=Observatorium: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionReport: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionStatus: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=Deployable: provided API should have an example annotation Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerDiagnoseConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=HelmRelease: provided API should have an example annotation Warning: Value app.k8s.io/v1beta1, Kind=Application: provided API should have an example annotation For advanced-cluster-management.v2.6.1: Warning: Value advanced-cluster-management.v2.6.1: owned CRD "observatoria.core.observatorium.io" has an empty description Warning: Value advanced-cluster-management.v2.6.1: owned CRD "submarinerconfigs.submarineraddon.open-cluster-management.io" has an empty description Warning: Value advanced-cluster-management.v2.6.1: owned CRD "submarinerdiagnoseconfigs.submarineraddon.open-cluster-management.io" has an empty description Warning: Value advanced-cluster-management.v2.6.1: channel(s) ["release-2.6"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value advanced-cluster-management.v2.6.1: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/ Warning: Value : (advanced-cluster-management.v2.6.1) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value apps.open-cluster-management.io/v1, Kind=PlacementRule: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1beta1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=HelmRelease: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1, Kind=Deployable: provided API should have an example annotation Warning: Value app.k8s.io/v1beta1, Kind=Application: provided API should have an example annotation Warning: Value core.observatorium.io/v1alpha1, Kind=Observatorium: provided API should have an example annotation Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerConfig: provided API should have an example annotation Warning: Value submarineraddon.open-cluster-management.io/v1alpha1, Kind=SubmarinerDiagnoseConfig: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=GitOpsCluster: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionReport: provided API should have an example annotation Warning: Value apps.open-cluster-management.io/v1alpha1, Kind=SubscriptionStatus: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	"OpenShift Platform Plus" "Red Hat Advanced Cluster Management for Kubernetes"	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
amq-streams	NOT COMPLY Following those does NOT complies: (+) . amq-streams-2.x amq-streams-2.1.x amq-streams-2.0.x amq-streams-1.8.x amq-streams-1.x Following those complies: stable	USED	FIX ERRORS AND WARNINGS (+) For amqstreams.v2.1.0-8: Owned CRDs do not have resources specified entityOperator does not have a spec descriptor kafka does not have a spec descriptor zookeeper does not have a spec descriptor tls does not have a spec descriptor config does not have a spec descriptor consumer does not have a spec descriptor producer does not have a spec descriptor http does not have a spec descriptor config does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor config does not have a spec descriptor clusters does not have a spec descriptor mirrors does not have a spec descriptor goals does not have a spec descriptor pods does not have a spec descriptor kafkas.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormakers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkabridges.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkatopics.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkausers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnectors.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormaker2s.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkarebalances.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status strimzipodsets.core.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for entityOperator Add a spec descriptor for kafka Add a spec descriptor for zookeeper Add a spec descriptor for tls Add a spec descriptor for config Add a spec descriptor for consumer Add a spec descriptor for producer Add a spec descriptor for http Add a spec descriptor for config Add a spec descriptor for authentication Add a spec descriptor for authorization Add a spec descriptor for config Add a spec descriptor for clusters Add a spec descriptor for mirrors Add a spec descriptor for goals Add a spec descriptor for pods For amqstreams.v2.0.1-3: Owned CRDs do not have resources specified entityOperator does not have a spec descriptor kafka does not have a spec descriptor zookeeper does not have a spec descriptor tls does not have a spec descriptor config does not have a spec descriptor consumer does not have a spec descriptor producer does not have a spec descriptor http does not have a spec descriptor config does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor config does not have a spec descriptor clusters does not have a spec descriptor mirrors does not have a spec descriptor goals does not have a spec descriptor Add a spec descriptor for entityOperator Add a spec descriptor for kafka Add a spec descriptor for zookeeper Add a spec descriptor for tls Add a spec descriptor for config Add a spec descriptor for consumer Add a spec descriptor for producer Add a spec descriptor for http Add a spec descriptor for config Add a spec descriptor for authentication Add a spec descriptor for authorization Add a spec descriptor for config Add a spec descriptor for clusters Add a spec descriptor for mirrors Add a spec descriptor for goals kafkas.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormakers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkabridges.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkatopics.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkausers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnectors.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormaker2s.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkarebalances.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For amqstreams.v1.8.4: Owned CRDs do not have resources specified kafka does not have a spec descriptor zookeeper does not have a spec descriptor entityOperator does not have a spec descriptor tls does not have a spec descriptor tls does not have a spec descriptor consumer does not have a spec descriptor producer does not have a spec descriptor http does not have a spec descriptor config does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor config does not have a spec descriptor clusters does not have a spec descriptor mirrors does not have a spec descriptor goals does not have a spec descriptor kafkas.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects2is.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormakers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkabridges.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkatopics.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkausers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnectors.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormaker2s.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkarebalances.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for kafka Add a spec descriptor for zookeeper Add a spec descriptor for entityOperator Add a spec descriptor for tls Add a spec descriptor for tls Add a spec descriptor for consumer Add a spec descriptor for producer Add a spec descriptor for http Add a spec descriptor for config Add a spec descriptor for authentication Add a spec descriptor for authorization Add a spec descriptor for config Add a spec descriptor for clusters Add a spec descriptor for mirrors Add a spec descriptor for goals Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead For amqstreams.v1.8.4: Owned CRDs do not have resources specified kafka does not have a spec descriptor zookeeper does not have a spec descriptor entityOperator does not have a spec descriptor tls does not have a spec descriptor tls does not have a spec descriptor consumer does not have a spec descriptor producer does not have a spec descriptor http does not have a spec descriptor config does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor config does not have a spec descriptor clusters does not have a spec descriptor mirrors does not have a spec descriptor goals does not have a spec descriptor kafkas.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects2is.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormakers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkabridges.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkatopics.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkausers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnectors.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormaker2s.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkarebalances.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for kafka Add a spec descriptor for zookeeper Add a spec descriptor for entityOperator Add a spec descriptor for tls Add a spec descriptor for tls Add a spec descriptor for consumer Add a spec descriptor for producer Add a spec descriptor for http Add a spec descriptor for config Add a spec descriptor for authentication Add a spec descriptor for authorization Add a spec descriptor for config Add a spec descriptor for clusters Add a spec descriptor for mirrors Add a spec descriptor for goals Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead For amqstreams.v2.1.0-8: Owned CRDs do not have resources specified entityOperator does not have a spec descriptor kafka does not have a spec descriptor zookeeper does not have a spec descriptor tls does not have a spec descriptor config does not have a spec descriptor consumer does not have a spec descriptor producer does not have a spec descriptor http does not have a spec descriptor config does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor config does not have a spec descriptor clusters does not have a spec descriptor mirrors does not have a spec descriptor goals does not have a spec descriptor pods does not have a spec descriptor kafkas.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormakers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkabridges.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkatopics.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkausers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnectors.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormaker2s.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkarebalances.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status strimzipodsets.core.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for entityOperator Add a spec descriptor for kafka Add a spec descriptor for zookeeper Add a spec descriptor for tls Add a spec descriptor for config Add a spec descriptor for consumer Add a spec descriptor for producer Add a spec descriptor for http Add a spec descriptor for config Add a spec descriptor for authentication Add a spec descriptor for authorization Add a spec descriptor for config Add a spec descriptor for clusters Add a spec descriptor for mirrors Add a spec descriptor for goals Add a spec descriptor for pods For amqstreams.v2.1.0-8: Owned CRDs do not have resources specified entityOperator does not have a spec descriptor kafka does not have a spec descriptor zookeeper does not have a spec descriptor tls does not have a spec descriptor config does not have a spec descriptor consumer does not have a spec descriptor producer does not have a spec descriptor http does not have a spec descriptor config does not have a spec descriptor authentication does not have a spec descriptor authorization does not have a spec descriptor config does not have a spec descriptor clusters does not have a spec descriptor mirrors does not have a spec descriptor goals does not have a spec descriptor pods does not have a spec descriptor kafkas.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnects.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormakers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkabridges.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkatopics.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkausers.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkaconnectors.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkamirrormaker2s.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status kafkarebalances.kafka.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status strimzipodsets.core.strimzi.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for entityOperator Add a spec descriptor for kafka Add a spec descriptor for zookeeper Add a spec descriptor for tls Add a spec descriptor for config Add a spec descriptor for consumer Add a spec descriptor for producer Add a spec descriptor for http Add a spec descriptor for config Add a spec descriptor for authentication Add a spec descriptor for authorization Add a spec descriptor for config Add a spec descriptor for clusters Add a spec descriptor for mirrors Add a spec descriptor for goals Add a spec descriptor for pods	CHECK THE WARNINGS (+) For amqstreams.v2.1.0-8: Warning: Value amqstreams.v2.1.0-8: channel(s) ["amq-streams-2.x" "amq-streams-2.1.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For amqstreams.v2.0.1-3: Warning: Value amqstreams.v2.0.1-3: unable to find the resource requests for the container: (strimzi-cluster-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amqstreams.v2.0.1-3: channel(s) ["amq-streams-2.x" "amq-streams-2.0.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For amqstreams.v1.8.4: Warning: Value amqstreams.v1.8.4: unable to find the resource requests for the container: (strimzi-cluster-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amqstreams.v1.8.4: channel(s) ["amq-streams-1.8.x" "amq-streams-1.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead For amqstreams.v1.8.4: Warning: Value amqstreams.v1.8.4: unable to find the resource requests for the container: (strimzi-cluster-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value amqstreams.v1.8.4: channel(s) ["amq-streams-1.8.x" "amq-streams-1.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : found olm.properties annotation, please define these properties in metadata/properties.yaml instead For amqstreams.v2.1.0-8: Warning: Value amqstreams.v2.1.0-8: channel(s) ["amq-streams-2.x" "amq-streams-2.1.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For amqstreams.v2.1.0-8: Warning: Value amqstreams.v2.1.0-8: channel(s) ["amq-streams-2.x" "amq-streams-2.1.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming	[Deep Insights]	"Red Hat Integration" "Red Hat AMQ"	RBAC requested for the API(s): (apiGroups/resources): policy/poddisruptionbudgets (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED
external-dns-operator	NOT COMPLY Following those does NOT complies: (+) . alpha Following those complies: stable-v1.0	USED	FIX ERRORS AND WARNINGS (+) For external-dns-operator.v0.1.2: Owned CRDs do not have resources specified provider does not have a spec descriptor source does not have a spec descriptor externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for provider Add a spec descriptor for source For external-dns-operator.v1.0.0: domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor zones does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor zones does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor zones does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor domains does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor zones does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor zones does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor zones does not have a spec descriptor domains does not have a spec descriptor provider does not have a spec descriptor source does not have a spec descriptor domains does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for zones Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for zones Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for zones Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for domains Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for zones Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for zones Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for zones Add a spec descriptor for domains Add a spec descriptor for provider Add a spec descriptor for source Add a spec descriptor for domains externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status externaldnses.externaldns.olm.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status	CHECK THE WARNINGS (+) For external-dns-operator.v0.1.2: Warning: Value external-dns-operator.v0.1.2: channel(s) ["alpha"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming For external-dns-operator.v1.0.0:	[Basic Install] (+) Check the capabilities doc to know how to improve it.	NOT ADDED		USED	NOT USED
file-integrity-operator	NOT COMPLY Following those does NOT complies: (+) . release-0.1 4.7	USED	FIX ERRORS AND WARNINGS (+) For file-integrity-operator.v0.1.30: Owned CRDs do not have resources specified config does not have a spec descriptor debug does not have a spec descriptor Warning: Value fileintegrity.openshift.io/v1alpha1, Kind=FileIntegrityNodeStatus: provided API should have an example annotation Add a spec descriptor for config Add a spec descriptor for debug fileintegrities.fileintegrity.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For file-integrity-operator.v0.1.13: config does not have a spec descriptor debug does not have a spec descriptor Owned CRDs do not have resources specified Add a spec descriptor for config Add a spec descriptor for debug fileintegrities.fileintegrity.openshift.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Warning: Value fileintegrity.openshift.io/v1alpha1, Kind=FileIntegrityNodeStatus: provided API should have an example annotation	CHECK THE WARNINGS (+) For file-integrity-operator.v0.1.30: Warning: Value file-integrity-operator.v0.1.30: channel(s) ["release-0.1"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (file-integrity-operator.v0.1.30) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value fileintegrity.openshift.io/v1alpha1, Kind=FileIntegrityNodeStatus: provided API should have an example annotation For file-integrity-operator.v0.1.13: Warning: Value file-integrity-operator.v0.1.13: unable to find the resource requests for the container: (file-integrity-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value file-integrity-operator.v0.1.13: channel(s) ["4.7"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (file-integrity-operator.v0.1.13) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. Warning: Value fileintegrity.openshift.io/v1alpha1, Kind=FileIntegrityNodeStatus: provided API should have an example annotation	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): events.k8s.io/events (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	USED	NOT USED
fuse-console	NOT COMPLY Following those does NOT complies: (+) . 7.9.x 7.11.x 7.10.x	SHOULD SUPPORT	FIX ERRORS AND WARNINGS (+) For fuse-console.v7.9.0: Owned CRDs do not have resources specified type does not have a spec descriptor resources does not have a spec descriptor Add a spec descriptor for type Add a spec descriptor for resources hawtios.hawt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status For fuse-console.v7.11.0-0.1662457143.p: Owned CRDs do not have resources specified resources does not have a spec descriptor type does not have a spec descriptor auth does not have a spec descriptor hawtios.hawt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for resources Add a spec descriptor for type Add a spec descriptor for auth For fuse-console.v7.10.3-0.1655306919.p: Owned CRDs do not have resources specified resources does not have a spec descriptor type does not have a spec descriptor hawtios.hawt.io does not have status spec. Note thatAll objects that represent a physical resource whose state may vary from the user's desired intent SHOULD have a spec and a status. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status Add a spec descriptor for resources Add a spec descriptor for type	CHECK THE WARNINGS (+) For fuse-console.v7.9.0: Warning: Value fuse-console.v7.9.0: unable to find the resource requests for the container: (fuse-console-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-console.v7.9.0: channel(s) ["7.9.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-console.v7.9.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-console.v7.11.0-0.1662457143.p: Warning: Value fuse-console.v7.11.0-0.1662457143.p: channel(s) ["7.11.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-console.v7.11.0-0.1662457143.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects. For fuse-console.v7.10.3-0.1655306919.p: Warning: Value fuse-console.v7.10.3-0.1655306919.p: unable to find the resource requests for the container: (fuse-console-operator). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/ Warning: Value fuse-console.v7.10.3-0.1655306919.p: channel(s) ["7.10.x"] are not following the recommended naming convention: https://olm.operatorframework.io/docs/best-practices/channel-naming Warning: Value : (fuse-console.v7.10.3-0.1655306919.p) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.	[Seamless Upgrades] (+) Check the capabilities doc to know how to improve it.	NOT ADDED	RBAC requested for the API(s): (apiGroups/resources): batch/cronjobs (+) ATTENTION: See the guide and ensure that the Operator does not uses the versions that will be removed.	NOT USED	NOT USED