You can perform Red Hat Container certification by using a custom container registry. This enables you to provide an access token to the registry, which thereby helps to verify the availability of the container images for users. Also, it ensures that the container image can be scanned by the security scanner and published on the Red Hat Ecosystem Catalog. Custom registries employ diverse authentication methods, and the Red Hat Software certification program supports the following authentication methods along with the standard OCI registry API:

• Bearer Authentication
• OAuth2
• Basic Authentication

For more details about the authentication methods, see Supported auth methods.

If you are using a public registry—such as DockerHub, GitLab, GitHub, or a similar registry, provide a Docker configuration file. Do this if the registry enforces rate limits on unauthenticated or anonymous access. Include valid authentication credentials for the specified registry.

Without this configuration, Red Hat certification systems can exceed the allowed request limits, preventing it from certifying or serving your container.

For operator-based CNI and CSI certification workflows, functional certification tests are credited only for the architectures on which the testing is conducted. You will need to provide multiple architecture-specific functional test runs for each supported architecture.

For CSI components, each protocol is tested in a separate test run for each architecture. A minimum of one protocol per architecture is required for certification. You can use supplemental certification requests to extend protocol coverage to additional architectures.

When running certification tests multiple times for different architectures or protocols for the same Red Hat product and partner product version, all results are submitted to the same functional certification.