This is unreleased documentation for SUSE® Rancher Manager v2.16 (Unreleased).

SUSE Customer Center Registration

SUSE Rancher Prime customers can register Rancher Manager with the SUSE Customer Center (SCC).

Registering your Rancher Manager instance with the SUSE Customer Center (SCC) unlocks unified visibility and control over your enterprise infrastructure, giving you a single pane of glass to track subscription usage alongside your SLES landscape. While your software currently continues to function seamlessly with full capabilities and zero operational lockouts if you choose not to register, completing this step now ensures you get the full management benefits, insights, and compliance backing for your ecosystem.

When logging in to SCC, you may see multiple registration codes listed under your organization. Ensure you select a code corresponding to an active SUSE Rancher Prime subscription.

There is no limit on the number of Rancher Manager instances that can be registered using the same registration code, and each instance is registered independently.

Prerequisites

Registering your Rancher Manager instance with SCC requires a SUSE account. If you don’t have a SUSE account yet, create one.
You must have access to your organization. Ask your organization’s administrator to add you to the account. See the SCC documentation and SCC FAQ for details. If you know your organization’s registration code, enter it when prompted.

Register with SUSE Customer Center

From the Rancher UI, go to Global Settings > Registration. You can also check the Notification Center (bell icon) in the upper-right corner for a "Rancher Prime Registration" notification and select Register Now. This redirects you to the Registration page under Global Settings.

You have the option to register your Rancher Manager instance with SCC online or offline.

Online Registration

You can register online through the Rancher UI or with Helm.

Obtain Registration Code

Before proceeding, you must obtain the registration code for your Rancher Manager subscription on SCC. To get the registration code:

Log in to SCC.
Navigate to My Organizations and select the organization with your Rancher Manager subscription.
Find your Registration code under Organization > Subscriptions > Subscription Information.

Rancher UI

From the Rancher UI, copy the registration code into the Registration code field and select Register. If successful, the Status becomes Active, and the Product Name, Expiration date and Registration mode are displayed.

Helm

After you have obtained your registration code from SCC, you can register your Rancher Manager instance through Helm.

Entrypoint Secret

To follow security best practices in production or GitOps environments, avoid storing registration codes in plain text. Instead, manually create an entrypoint secret before installation to allow the SCC Operator to detect and consume the registration data automatically.

Create the SCC system namespace. The SCC Operator expects registration data to reside in the cattle-scc-system namespace.
```
kubectl create namespace cattle-scc-system
```
Create a secret named scc-registration containing your registration code. This secret can be managed through external secret managers to keep it encrypted in Git.
```
kubectl create secret generic scc-registration \
  --namespace cattle-scc-system \
  --from-literal=regCode=<REGISTRATION-CODE-FROM-SCC>
```
Enable registration in your values.yaml but leave the regCode field empty. When registration.enabled is true and no code is provided in the values, the operator looks for an existing scc-registration secret in the cattle-scc-system namespace.
```
registration:
  enabled: true
  regCode: ""
```

Deploy Rancher using your updated values.yaml:

helm install rancher rancher-prime/rancher \
  --namespace cattle-system \
  --values values.yaml

To verify that the registration was successful using the manually created secret, check the logs of the SCC-Operator or the status of the registration in the Rancher UI under Global Settings > Registration.

Helm Parameters

For testing or non-production environments, you can pass the registration code directly during the Helm install command:

helm install rancher rancher-prime/rancher \
  --namespace cattle-system \
  --set registration.enabled=true \
  --set registration.regCode=<REGISTRATION-CODE-FROM-SCC>

Alternatively, you can update values.yaml to enable registration and add your registration code.

registration:
  enabled: true
  regCode: "<REGISTRATION-CODE>"

Then, deploy Rancher using the updated values file:

helm install rancher rancher-prime/rancher
  --namespace cattle-system
  --values values.yaml

Offline Registration

If you are using Rancher in an air-gapped environment, you can register offline through the Rancher UI or with Helm.

Rancher UI

An SCC Organization Admin must get your registration certificate, as regular users do not have access.

From the Rancher UI, select Download registration request to download the registration request file.
Select Visit SCC to use the SCC offline registration tool and get the registration certificate.
1. Upload the registration request file.
2. Select your Organization and Subscription.
3. Select Download Offline Certificate and save the registration certificate file.
Return to the Rancher UI, select Upload certificate and register to upload the registration certificate. If successful, the Status becomes Active, and the Product Name, Expiration date and Registration mode are displayed.

Helm

In values.yaml, enable registration, comment out regCode and set the mode to offline.
```
registration:
  enabled: true
  # regCode: ""
  mode: offline
```
Run the Helm install command helm install rancher rancher-prime/rancher and verify installation is successful.
Before proceeding, use the following Bash command to check that the SCC-Operator has successfully created a secret in the cattle-scc-system namespace. After the secret is created, it outputs Secret created!.
```
for i in {1..100}; do kubectl wait --for=create secret/scc-registration -n cattle-scc-system --timeout=3s &> /dev/null && echo "Secret created!" && break || { echo "Not ready yet..."; sleep 3; }; done
```

Using kubectl, retrieve the registration request file and save it locally.

kubectl get secrets -n cattle-scc-system \
-l scc.cattle.io/secret-role=offline-request,scc.cattle.io/scc-hash=$(kubectl get secrets \
-n cattle-scc-system scc-registration -o yaml|yq '.metadata.labels["scc.cattle.io/scc-hash"]') \
-o yaml | yq '.items[0].data.request' > offline.base64

Select Visit SCC to use the SCC offline registration tool.
1. Upload the registration request file.
2. Select your Organization and Subscription.
3. Select Download Offline Certificate and save the registration certificate file.
Upload the registration certificate file to your Rancher Manager instance using kubectl or Helm.
- kubectl:
  kubectl patch secret -n cattle-scc-system scc-registration \ --type='merge' -p "{\"data\": {\"certificate\": \"$(cat <your Offline Cert file> )\"}}"
- Helm:
  
  Add your registration certificate using the certificate value field, and then helm upgrade Rancher.
  certificate: {}

Post-Registration

After registering your Rancher Manager instance with SCC, several updates occur across both the local Rancher Manager instance and the central SUSE Customer Center.

Rancher Application

Status Update: Under Global Settings > Registration, the subscription status updates to Active, displaying your Product Name, Expiration Date, and Registration Mode.
Background Telemetry Sync: The embedded scc-operator begins transmitting technical metrics (such as downstream cluster counts, vCPU counts, node capacity, and the server URL) to SCC at regular intervals over HTTPS.

Viewing Registered Instances in SCC

You can centrally manage and track your organization’s deployed Rancher Manager instances in SCC.

To view registered Rancher Manager instances in SCC:

Log in to SUSE Customer Center and select your organization.
Select Systems in the top navigation menu.
Locate your relevant Rancher Manager instance in the system list and select the instance name to open a detailed overview.

Alternatively, you can navigate to the Subscriptions view in the top navigation menu, select your SUSE Rancher Prime subscription, and view the Registered Systems to view all instances under that specific subscription.

Deregister from SUSE Customer Center

Organization administrators can deregister Rancher Manager instances from SCC. Deregistering a system removes it from being tracked in the SCC server inventory.

If you deregister a system behind the Repository Mirroring Tool (RMT) registration proxy, you must also remove the system from the proxy itself. Otherwise, active systems will reappear in SCC.

Online Deregistration Steps

Go to Global Settings > Registration.
Find your Product Registration under Online Registration or Offline Registration and select Deregister.

Offline Deregistration Steps

Log in to SUSE Customer Center and your Rancher application.
In the Rancher UI, select Cluster Management, then select your local cluster.
Search for Registration on your local cluster using the search field to find the Registration object.
View the Registration objects YAML to identify the SCC System ID (.status.sccSystemID).
From the SCC portal, select the Systems tab and locate the matching Rancher Manager instance using the SCC System ID.
Select Deregister to remove the system from SCC.
Return to Rancher and navigate to Global Settings > Registration.
Select Deregister to remove the registration from Rancher.

Telemetry

To improve service and stability, your Rancher Manager server securely sends technical telemetry, including deployment details, version, and usage metrics to SUSE.

The key benefit of this is gaining a unified view in the SUSE Customer Center, allowing you to manage your Rancher installations, monitor subscription compliance, and track subscription usage alongside your existing SLES landscape in a single, comprehensive pane.

The following table details the system attributes included in the telemetry data.

System attribute	Example
Product name	Rancher Manager Prime
Product version	2.16.1
Architecture	x86_64
Server URL	The management URL of the RMS
Cluster UUID	UUID of the k8s cluster hosting the RMS instance
Install UUID	UUID of the RMS instance
Git hash	Hash of the RMS build
Feature Flags	Enabled on the RMS instance

System attribute

Example

Product name

Rancher Manager Prime

Product version

2.16.1

Architecture

x86_64

Server URL

The management URL of the RMS

Cluster UUID

UUID of the k8s cluster hosting the RMS instance

Install UUID

UUID of the RMS instance

Git hash

Hash of the RMS build

Feature Flags

Enabled on the RMS instance