3 Installing SUSE Private Registry using the Rancher UI #

Log in to Rancher.

Click menu:☰[] and select Cluster Management.

Click Explore next to your cluster, usually local.

Select Cluster › Projects/Namespaces.

Click Create Namespace in a project or under Not in a Project.

Enter suse-registry as the name and click Create.

In the cluster view, select Apps › Repositories and click Add Repository.

Select OCI Repository as the target.

Enter a name, such as suse-private-registry.

In OCI Repository Host URL, enter oci://registry.suse.com/private-registry/private-registry-helm.

In Authentication, select Create an HTTP Basic Auth Secret and enter the SCC user name and password.

Click Add Repository.

Wait until the repository state changes to Active.

Select Storage › Secrets and click Create.

Select Registry as the secret type.

In the Namespace list, select the suse-registry namespace and enter suse-registry as the secret name. The chart expects this secret name by default.

From the registry list, select Custom, then enter registry.suse.com as the domain.

Enter the SCC user name and password and click Create.

Optional: To use your own certificate, click Create again, select TLS Certificate, enter suse-registry-tls as the name and paste the certificate and private key.

Select Apps › Charts.

Search for suse-private-registry. If the chart is missing, select Apps › Repositories, select the repository and click Refresh.

Note

The catalog can show two entries. Select suse-private-registry, which has the description and the latest version.

Click the chart and review the README.md.

Click Install this version.

On the Metadata step, select the suse-registry namespace and enter spr as the release name.

Click Next.

On the Values step, configure the chart as described in Section 3.6, “How do I configure Private Registry during the installation?”.

Click Install.

On the Values step, select Edit Options. The form groups the settings into tabs.

On the Expose tab, enter the FQDN in Ingress Host and the controller in Ingress Class Name, such as traefik.

On the General tab, enter https://<PRIVATE_REGISTRY_FQDN> in External URL and set Harbor Admin Password.

Optional: Use the External Services, Deployment and Storage tabs to use external Redis or database services, set replica counts and set volume sizes and the storage class.

Select Compare Changes to review the differences from the defaults.

On the Values step, select Edit YAML next to Edit Options. The editor shows all chart values with their defaults.

Figure 3.5: Editing the chart values as YAML #

 

Change the values that you need, for example:

externalURL: https://<PRIVATE_REGISTRY_FQDN>
harborAdminPassword: "<MY_PASSWORD>"
imagePullSecrets:
  - name: suse-registry
expose:
  type: ingress
  tls:
    enabled: true
    certSource: auto
  ingress:
    className: <INGRESS_CLASS>
    hosts:
      core: <PRIVATE_REGISTRY_FQDN>
persistence:
  enabled: true

To use your own certificate, create a TLS secret first, set certSource to secret and set expose.tls.secret.secretName. For all values, see Appendix A, Overriding the SUSE Private Registry Helm chart.

Select Apps › Installed Apps and check that the release status is Deployed.

Figure 3.6: Installed release #

 

Select Workloads › Pods and check that all pods in the suse-registry namespace are Running.

Open https://<PRIVATE_REGISTRY_FQDN> and log in as admin.

Select Apps › Installed Apps.

Click menu:⋮[] for the release and select Edit / Change Version.

Select the new chart version and review the values.

Click Upgrade.