1. To complete your product listing details, click Start.

   The Product Information tab opens.

2. Enter all the essential product details and click Save.

1. To complete your company profile information, click Start. After entering all the details, click Submit.
2. To modify the existing details, click Review. The Account Details page opens.
3. Review and modify the Company profile information and click Submit.

1. Click Start. You are redirected to the Components tab.

   To add a new or existing product component, click Add component.

2. For adding a new component,

   1. In the Component Name text box, enter the component name.
   2. For What kind of standalone component are you creating? select the component that you wish to certify. For example, for certifying a non containerized component, select Non-containerized Application.

   3. For Red Hat Enterprise Linux Version, select the major RHEL version for which you are certifying your component.

      Note

      You can’t modify the version after creating the product listing.

   4. Click Create new component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. To certify the components for your listing, click Start. If you have existing product components, you can view the list of Attached Components and their details:

   1. Name
   2. Certification
   3. Security
   4. Type
   5. Created
   6. Click more options to archive or remove the components
2. Select the components for certification.

1. Product contacts - Provides Product marketing and Technical contact information.

   1. Click Add contacts to product to provide the contact information
   2. Click Edit to update the information.

2. Components in product - Provides the list of the components attached to the product along with their last updated information.

   1. Click Add components to product to add new or existing components to your product.
   2. Click Edit components to update the existing component information.

1. Join the Red Hat Connect for Technology Partner Program.
2. Agree to the program terms and conditions.

3. Create your product listing by selecting your desired product category. You can select from the available product categories:

   1. Containerized Application
   2. Standalone Application
   3. OpenStack Infrastructure
4. Complete your company profile.
5. Add components to the product listing.
6. Certify components for your product listing.

1. Build your container image.
2. Upload your container image to your chosen registry. You can choose any registry of your choice.

3. Download the Preflight certification utility.
4. Run Preflight with your container image.
5. Submit results on Red Hat Partner Connect.

Prerequisites

1. Podman is installed on your system.
2. You have a Dockerfile that defines the image you want to build for multiple architectures.
3. You have a Quay.io account or any other container registry account.

Procedure

1. Prepare Your Dockerfile.
2. Build and push the multi-arch container Images. Check the podman-manifest documentation for instructions on building and pushing the multi-arch container images.

1. To complete your product listing details, click Start.

   The Product Information tab opens.

2. Enter all the essential product details and click Save.

1. To complete your company profile information, click Start. After entering all the details, click Submit.
2. To modify the existing details, click Review. The Account Details page opens.
3. Review and modify the Company profile information and click Submit.

1. To accept the legal agreements, click Start.
2. To preview or download the agreement, click Review.

1. Click Start. You are redirected to the Components tab.

   To add a new or existing product component, click Add component.

2. For adding a new component,

   1. In the Component Name text box, enter the component name.

   2. For What kind of standalone component are you creating? select the component that you wish to certify. For example, for certifying your containers, based on your requirements select from the following options:

      1. Container Image
      2. Containerized application for RHEL
      3. Containerized application for OpenStack
   3. Click Next.

   4. For Red Hat Enterprise Linux Version, select the major RHEL version for which you are certifying your component.

      Note

      You can’t modify the version after creating the product listing.

   5. Click Create new component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. To certify the components for your listing, click Start. If you have existing product components, you can view the list of Attached Components and their details:

   1. Name
   2. Certification
   3. Security
   4. Type
   5. Created
   6. Click more options to archive or remove the components
2. Select the components for certification.

1. Product contacts - Provides Product marketing and Technical contact information.

   1. Click Add contacts to product to provide the contact information
   2. Click Edit to update the information.

2. Components in product - Provides the list of the components attached to the product along with their last updated information.

   1. Click Add components to product to add new or existing components to your product.
   2. Click Edit components to update the existing component information.

1. To add a new or existing product component, click Add component.

2. For adding a new component perform the steps,

   1. In the Component Name text box, enter the component name.
   2. For What kind of standalone component are you creating? select the component that you wish to certify. For example, for certifying your containers, select Container Image.
   3. Click Next.

   4. On the Create and Add component page, select the preferred OS Content-Type and Distribution Method for the component:

      1. For What base image does your container use?, select the type of image that you want to use for your component:

         1. Red Hat Universal Base Image - You can distribute UBI-based container images through the Red Hat Container registry or any other third-party registry.
         2. Red Hat Enterprise Linux - You can distribute RHEL-based container images through the Red Hat Container registry only.

      2. For Select your preferred Distribution Method, select the container registry that you will use for distributing your container images. Customers will pull your container images from this location and in all the following methods your container images remain hosted on a registry that you manage. Red Hat recommends Quay.io to host your images, but you can use any Kubernetes-compatible registry.

         1. Red Hat Container Registry - Select this option, if you want Red Hat to distribute your containers through Red Hat’s container registry. Select the I need Red Hat to host my registry check box. When you select this option, images with this distribution method are hosted on your container registry, but are distributed to customers through a Red Hat registry proxy address. Customers will have access to your containers without adding registries to their configuration, but you will not have visibility on customer-specific download metrics or other usage data from the proxy.
         2. Your own Container Registry - Select this option to publish your certified containers on your registry. When using your own third-party registry, customers will need to authenticate to your registry, to pull your certified containers, and use your product. In disconnected environments, customers must add your registry to their Red Hat platforms to install your certified containers. NOTE - Red Hat recommends self-hosting on your registry because you can access your entire container metrics and have full control of the access of your product. Red Hat recommends using Quay.io for this purpose, however, you can use any Kubernetes-compatible registry.
   5. Click Add Component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. To add a new or existing product component, click Add component.

2. For adding a new component perform the steps,

   1. In the Component Name text box, enter the component name.
   2. For What kind of standalone component are you creating? select the component that you wish to certify. For example, select Containerized application for RHEL.
   3. Click Next.

   4. On the Create and Add component page, select the preferred RHEL version and Distribution Method for the component:

      1. For What major version of RHEL will you be certifying your image for?, select the preferred RHEL version:

         1. 8

         2. 9

            Note

            You cannot modify the version after creating the product component.

      2. For Distribution Method, select the container registry that you will use for distributing your container images. Customers will pull your container images from this location and in all the following methods your container images remain hosted on a registry that you manage. Red Hat recommends Quay.io to host your images, but you can use any Kubernetes-compatible registry.

         1. Red Hat Container Registry - Select this option, if you want Red Hat to distribute your containers through Red Hat’s container registry. Select the I need Red Hat to host my registry check box. When you select this option, images with this distribution method are hosted on your container registry but are distributed to customers through a Red Hat registry proxy address. Customers will have access to your containers without adding registries to their configuration, but you will not have visibility on customer-specific download metrics or other usage data from the proxy.
         2. Your own Container Registry - Select this option to publish your certified containers on your registry. When using your own third-party registry, customers will need to authenticate to your registry to pull your certified containers and use your product. In disconnected environments, customers must add your registry to their Red Hat platforms to install your certified containers. NOTE - Red Hat recommends self-hosting on your registry because you can your entire container metrics and have full control of the access of your product. Red Hat recommends using Quay.io for this purpose, however, you can use any Kubernetes-compatible registry.
   5. Click Add Component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. To add a new or existing product component, click Add component.

2. For adding a new component, in the Component Name text box, enter the component name.

   1. For What kind of standalone component are you creating? select the component that you wish to certify. For example, for certifying a containerized application for Red Hat OpenStack platform, select Containerized application for OpenStack.
   2. For What major version of OpenStack will you be certifying your image for? version 17 is enabled by default. You cannot modify this field.
   3. Click Create new Component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.

   2. Click Attach existing component.

      Note

      You can add one component to multiple products listings. All attached components must be published before the product listing can be published.

      After attaching components, you can view the list of Attached Components and their details:

      1. Name
      2. Certification
      3. Security
      4. Type
      5. Created
      6. Click more options to archive or remove the attached components

1. Join the Red Hat Connect for Technology Partner Program.
2. Agree to the program terms and conditions.

3. Create your product listing by selecting your desired product category. You can select from the available product categories:

   1. Containerized Application
   2. Standalone Application
   3. OpenStack Infrastructure
4. Complete your company profile.
5. Add components to the product listing.
6. Certify components for your product listing.

1. Fork the Red Hat upstream repository.
2. Install and run the Red Hat certification pipeline on your test environment.
3. Review the test results and troubleshoot, if any issues.
4. Submit the certification results to Red Hat through a pull request.
5. If you want Red Hat to run all the tests then create a pull request. This triggers the certification hosted pipeline to run all the certification checks on Red Hat infrastructure.

1. To complete your product listing details, click Start.

   The Product Information tab opens.

2. Enter all the essential product details and click Save.

1. To complete your company profile information, click Start. After entering all the details, click Submit.
2. To modify the existing details, click Review. The Account Details page opens.
3. Review and modify the Company profile information and click Submit.

1. To accept the legal agreements, click Start.
2. To preview or download the agreement, click Review.

1. Click Start. You are redirected to the Components tab.

   To add a new or existing product component, click Add component.

2. For adding a new component,

   1. In the Component Name text box, enter the component name.
   2. For What kind of OpenShift component are you creating? select the component that you wish to certify. For example, for certifying your operators, select Operator Bundle.
   3. Click Next.

   4. Specialized Certification - This feature allows you to certify a specialized operator.

      1. Select My operator is a CNI or CSI checkbox, if you want to certify a specialized operator. …​Select the required operator:

         1. Container Network Interface (CNI)
         2. Cloud Storage Interface (CSI)

   5. Publication Options - Select one of the following options for publishing your operator:

      1. Web catalog only (catalog.redhat.com) - The operator is published to the Red Hat Container Catalog and is not visible on Red Hat OpenShift OperatorHub. This is the default option when you create a new operator component and this option is suitable for partners who do not want their operator publicly installable within OpenShift, but require a proof of certification. Select this option only if you have a distribution, entitlement, or other business requirements that is not otherwise accommodated within the OpenShift In-product Catalog (Certified) option.
      2. OpenShift In-product Catalog (Certified) - The operator is listed on the Red Hat Container Catalog and published to the certified operator index embedded in the OperatorHub of OpenShift.
   6. Click Add component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. To certify the components for your listing, click Start. If you have existing product components, you can view the list of Attached Components and their details:

   1. Name
   2. Certification
   3. Security
   4. Type
   5. Created
   6. Click more options to archive or remove the components
2. Select the components for certification.

1. Product contacts - Provides Product marketing and Technical contact information.

   1. Click Add contacts to product to provide the contact information
   2. Click Edit to update the information.

2. Components in product - Provides the list of the components attached to the product along with their last updated information.

   1. Click Add components to product to add new or existing components to your product.
   2. Click Edit components to update the existing component information.

1. Join the Red Hat Connect for Technology Partner Program.
2. Agree to the program terms and conditions.

3. Create your product listing by selecting your desired product category. You can select from the available product categories:

   1. Containerized Application
   2. Standalone Application
   3. OpenStack Infrastructure
4. Complete your company profile.
5. Add components to the product listing.
6. Certify components for your product listing.

1. Fork the Red Hat upstream repository.
2. Install and run the chart verifier tool on your test environment.
3. Review the test results and troubleshoot, if any issues.
4. Submit the certification results to Red Hat through a pull request.

1. Run all the available checks for a chart available remotely using a universal resource identifier (uri), assuming that the kube config file is available at the location ${HOME}/.kube:

   $ podman run --rm -i                                  \
           -e KUBECONFIG=/.kube/config                   \
           -v "${HOME}/.kube":/.kube                     \
           "quay.io/redhat-certification/chart-verifier" \
           verify                                        \
           <chart-uri>

   In this command, chart-uri is the location of the chart archive available on the https uri. Ensure that the archive must be in .tgz format.

2. Run all the available checks for a chart available locally on your system, assuming that the chart is available on the current directory and the kube config file is available at the location ${HOME}/.kube:

   $ podman run --rm                                     \
           -e KUBECONFIG=/.kube/config                   \
           -v "${HOME}/.kube":/.kube                     \
           -v $(pwd):/charts                             \
           "quay.io/redhat-certification/chart-verifier" \
           verify                                        \
           /charts/<chart>

   In this command, chart-uri is the location of the chart archive available in your local directory. Ensure that the archive must be in .tgz format.

3. Run the following verify command to get the list of available options associated with the command along with its usage:

   $ podman run -it --rm quay.io/redhat-certification/chart-verifier verify --help

   The output of the command is similar to the following example:

   Verifies a Helm chart by checking some of its characteristics
   
   Usage:
     chart-verifier verify <chart-uri> [flags]
   
   Flags:
     -S, --chart-set strings           set values for the chart (can specify multiple or separate values with commas: key1=val1,key2=val2)
     -G, --chart-set-file strings      set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
     -X, --chart-set-string strings    set STRING values for the chart (can specify multiple or separate values with commas: key1=val1,key2=val2)
     -F, --chart-values strings        specify values in a YAML file or a URL (can specify multiple)
         --debug                       enable verbose output
     -x, --disable strings             all checks will be enabled except the informed ones
     -e, --enable strings              only the informed checks will be enabled
         --helm-install-timeout duration   helm install timeout (default 5m0s)
     -h, --help                        help for verify
         --kube-apiserver string       the address and the port for the Kubernetes API server
         --kube-as-group stringArray   group to impersonate for the operation, this flag can be repeated to specify multiple groups.
         --kube-as-user string         username to impersonate for the operation
         --kube-ca-file string         the certificate authority file for the Kubernetes API server connection
         --kube-context string         name of the kubeconfig context to use
         --kube-token string           bearer token used for authentication
         --kubeconfig string           path to the kubeconfig file
     -n, --namespace string            namespace scope for this request
     -V, --openshift-version string    set the value of certifiedOpenShiftVersions in the report
     -o, --output string               the output format: default, json or yaml
     -k, --pgp-public-key string       file containing gpg public key of the key used to sign the chart
     -W, --web-catalog-only            set this to indicate that the distribution method is web catalog only (default: true)
         --registry-config string      path to the registry config file (default "/home/baiju/.config/helm/registry.json")
         --repository-cache string     path to the file containing cached repository indexes (default "/home/baiju/.cache/helm/repository")
         --repository-config string    path to the file containing repository names and URLs (default "/home/baiju/.config/helm/repositories.yaml")
     -s, --set strings                 overrides a configuration, e.g: dummy.ok=false
     -f, --set-values strings          specify application and check configuration values in a YAML file or a URL (can specify multiple)
     -E, --suppress-error-log          suppress the error log (default: written to ./chartverifier/verifier-<timestamp>.log)
         --timeout duration            time to wait for completion of chart install and test (default 30m0s)
     -w, --write-to-file               write report to ./chartverifier/report.yaml (default: stdout)
   Global Flags:
         --config string   config file (default is $HOME/.chart-verifier.yaml)

4. Run a subset of the checks:

   $ podman run --rm -i                                  \
           -e KUBECONFIG=/.kube/config                   \
           -v "${HOME}/.kube":/.kube                     \
           "quay.io/redhat-certification/chart-verifier" \
           verify -enable images-are-certified,helm-lint      \
           <chart-uri>

5. Run all the checks except a subset:

   $ podman run --rm -i                                  \
           -e KUBECONFIG=/.kube/config                   \
           -v "${HOME}/.kube":/.kube                     \
           "quay.io/redhat-certification/chart-verifier" \
           verify -disable images-are-certified,helm-lint      \
           <chart-uri>

   Note

   Running a subset of checks is intended to reduce the feedback loop for development. To certify your chart, you must run all the required checks.

6. Provide chart-override values:

   $ podman run --rm -i                                  \
           -e KUBECONFIG=/.kube/config                   \
           -v "${HOME}/.kube":/.kube                     \
           "quay.io/redhat-certification/chart-verifier" \
           verify –chart-set default.port=8080                   \
           <chart-uri>

7. Provide chart-override values from a file located in the current directory:

   $ podman run --rm -i                                  \
           -e KUBECONFIG=/.kube/config                   \
           -v "${HOME}/.kube":/.kube                     \
           -v $(pwd):/values                             \
           "quay.io/redhat-certification/chart-verifier" \
           verify –chart-values /values/overrides.yaml              \
           <chart-uri>

1. Download and install the latest chart-verifier binary from the releases page.

2. Unzip the tarball binary by using the following command:

   $ tar zxvf <tarball>

3. Run the following command on the unzipped directory to perform all the Helm chart checks :

   $ ./chart-verifier verify <chart-uri>

   In this command, chart-uri is the location of the chart archive available on your server. Ensure that the archive must be in .tgz format. By default, the chart-verifier tool assumes that the kube config file is available at the default location $HOME/.kube. Set the environment variable to KUBECONFIG if the file is not available at the default location.

   The output of the chart-verifier includes the details of the tests executed along with a result status for each test. It also indicates whether each test is mandatory or recommended for Red Hat certification. For more detailed information, see Types of Helm chart checks.

1. To complete your product listing details, click Start.

   The Product Information tab opens.

2. Enter all the essential product details and click Save.

1. To complete your company profile information, click Start. After entering all the details, click Submit.
2. To modify the existing details, click Review. The Account Details page opens.
3. Review and modify the Company profile information and click Submit.

1. To accept the legal agreements, click Start.
2. To preview or download the agreement, click Review.

1. Click Start. You are redirected to the Components tab.

   To add a new or existing product component, click Add component.

2. For adding a new component,

   1. In the Component Name text box, enter the component name.
   2. For What kind of standalone component are you creating? select the component that you wish to certify. For example, for certifying your Helm Charts, select Helm Chart.
   3. Click Next.
   4. In the Chart Name text box, enter a unique name for your chart.

   5. Distribution Method - Select one of the following options for publishing your Helm Chart:

      1. Helm chart repository charts.openshift.io - The Helm chart is published to the Red Hat Helm chart repository, charts.openshift.io and the users can pull your chart from this repository.

         Note

         When you select the checkbox The certified helm chart will be distributed from my company’s repository, an entry about the location of your chart is added to the index of Red Hat Helm chart repository, charts.openshift.io.

      2. Web catalog only (catalog.redhat.com) - The Helm chart is not published to the Red Hat Helm chart repository, charts.openshift.io and is not visible on Red Hat OpenShift OperatorHub. This is the default option when you create a new component and this option is suitable for partners who do not want their Helm chart publicly installable within OpenShift, but require a proof of certification. Select this option only if you have a distribution, entitlement, or other business requirements that is not otherwise accommodated within the OpenShift In-product Catalog (Certified) option.
   6. Click Add component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. To certify the components for your listing, click Start. If you have existing product components, you can view the list of Attached Components and their details:

   1. Name
   2. Certification
   3. Security
   4. Type
   5. Created
   6. Click more options to archive or remove the components
2. Select the components for certification.

1. Product contacts - Provides Product marketing and Technical contact information.

   1. Click Add contacts to product to provide the contact information
   2. Click Edit to update the information.

2. Components in product - Provides the list of the components attached to the product along with their last updated information.

   1. Click Add components to product to add new or existing components to your product.
   2. Click Edit components to update the existing component information.

1. Section 31.1.2.1, “Certification onboarding for cnf”
2. Section 31.1.2.2, “Completing the product listing for cnf”
3. Section 31.1.2.3, “Publishing the product listing on the Red Hat Ecosystem Catalog”

1. Enter the Product Name.
2. Optional: Upload the Product Logo according to the defined guidelines.
3. Enter a Brief description and a Long description.
4. Click Save.

1. Optional: Enter the Title and Description.
2. Optional: To add additional features for your product, click + Add new feature.
3. Click Save.

1. Optional: Enter Quick start & configuration instructions.
2. Click Save.
3. Select Hide default instructions check box, if you don’t want to display them.

1. Select the Type drop-down menu, and enter the Title and Description of the resource.
2. Enter the Resource URL.
3. Optional: To add additional resources for your product, click + Add new Resource.
4. Click Save.

1. Enter Question and Answer.
2. Optional: To add additional FAQs for your product, click + Add new FAQ.
3. Click Save.

1. Enter the Support description, Support web site, Support phone number, and Support email address.
2. Click Save.

1. Enter the Marketing contact email address and Technical contact email address.
2. Optional: To add additional contacts, click + Add another.
3. Click Save.

1. Enter the License Agreement URL for the product and Privacy Policy URL.
2. Click Save.

1. Select the Product Category.
2. Enter the Key and Value to set up Search aliases.
3. Click Save.
4. Optional: To add additional key-value pair, click + Add new key-value pair.

1. To add a new or existing product component, click Add component.

2. For adding a new component,

   1. In the Component Name text box, enter the component name.

   2. In the Component Name text box, enter the component name. This name is not published and is only for internal use.

      Note

      Red Hat recommends including the product version in the component name to aid easy identification of the newly created CNF component. For example, <CompanyName ProductName> 1.2 - OCP 4.12.2)

   3. For What kind of OpenShift component are you creating? select the component that you wish to certify. For example, for certifying your CNF, select Cloud Native Function (CNF).
   4. Click Create new component.

3. For adding an existing component, from the Add Component dialog, select Existing Component.

   1. From the Available components list, search and select the components that you wish to certify and click the forward arrow. The selected components are added to the Chosen components list.
   2. Click Attach existing component.

1. Name
2. Certification
3. Security
4. Type
5. Created
6. Click more options to archive or remove the attached components

1. To request support, click Open a support case. See PAD - How to open & manage PAD cases, to open a PAD ticket.
2. To view the list of existing support cases, click View support cases.

1. Optional: In the Technical contact email address field, enter the email address of the image maintainer.
2. Optional: To add additional contacts for your component, click + Add new contact.
3. Click Save.

1. Section 32.1.2.1, “Certification on-boarding for CNI”
2. Section 32.1.2.2, “Certification testing for CNI”
3. Section 31.1.2.3, “Publishing the product listing on the Red Hat Ecosystem Catalog”