This is unreleased documentation for Vulnerability Scanner 0.13.0-dev.

Creating and Editing a Registry

The registry configuration form is used both to create a new registry and to edit an existing one.

For the equivalent CRD-based workflow, see Scanning Registries.

Configuration fields

Namespace: A registry is a namespaced resource, so you must choose the namespace it belongs to.
Registry: A unique name for the registry.
Description: A short description of the resource.
Type: The registry type. OCI distribution is supported by default.
URI: The URL of the registry.
CA Cert Bundle: A certificate used to connect to a secured registry on an internal network. This is typically needed for an air-gapped registry.
Allow insecure connections: Skips SSL/TLS verification. Use this only for testing against a trusted internal registry.
Authentication: The secret holding the credentials used to authenticate against the registry. Select an existing secret from the dropdown, or follow the Create secret link to create a new one. See Creating a registry secret.
Repositories to scan: The repositories to include in the scan. Add each one as a tag in the tag input box.
Scan Interval: How often a scan runs. Set this to Manual if you don’t want a periodic scan.
Filter by Platform: Limits the scope of the scan. You can add several platform filters, each identified by an operating system, architecture, and variant.

On the registry configuration page, use the link in the banner to create a new secret, or choose an existing secret from the dropdown.

When you create a new secret, the link opens the secret page in a new browser tab, using the same Rancher session. Create the secret from that page.

Select the Registry badge to create a registry secret.
Choose DockerHub and enter the username and password.
After you save the secret, it appears in the secret list.
Return to the original tab and open the Authentication dropdown to select the secret you just created.