To be certified for OpenShift, the Helm chart used to deploy your product must meet the following requirements:
| Requirement | Why is this needed? |
|---|---|
| Functionality of the product must be tested on OpenShift | OpenShift users know that the product has been tested on the container platform they use |
| Product must be supported on OpenShift | Customers can deploy with confidence knowing they have access to enterprise support |
| All containers used by the chart must be Red Hat Certified Containers | Operating system libraries in certified container images are covered by the Red Hat OpenShift support, and continuously monitored for security vulnerabilities. If you need to certify your container first, please follow this link |
| The chart's apiVersion field must be set to v2 | Chart must be compatible with Helm 3 (i.e. apiVersion v2), the Helm version supported in OpenShift |
| Chart must contain a README.md file | Provide basic information about the chart in human-readable format |
| Chart must set the kubeVersion field to indicate the minimum Kubernetes version supported | To ensure that the chart is supported on the target version of OpenShift |
| Chart must include one or more tests, located in the templates directory | To verify successful chart installation |
| Chart must include a values.yaml file and a values.schema.json file | Identify chart inputs and provide proper validation |
| Chart should not contain any CRDs | Life cycle of Custom Resource Definitions needs to be managed properly. An Operator is recommended for this task. |
| Chart must pass the helm lint command | Ensuring correct chart format |
| Chart must include the charts.openshift.io/name annotation with a human-readable name | Provide a name that can be used when displaying the chart in the OpenShift console |