Register Rancher Prime - RKE2
Steps to register Rancher Prime RKE2 Cluster in gopaddle
Rancher Prime RKE2 cluster can be registered in gopaddle either using its public IP address or a fully qualified domain name (FQDN) or securely via a Bastion Host or a Jump server.
1. Prepare Kubernetes Environment
Port Configuration
Configure Subject Alternative Names (SAN)
Add Subject Alternative Names (SAN) on the RKE2 server TLS cert. If SAN does not exist for the API endpoint, add the below in the cluster configuration.
a) Login to the RKE2 master node.
b) Create/edit the file /etc/rancher/rke2/config.yaml file with the below configuration :
tls-san:
<public-ip-address> # or <fully-qualified-domain-name>
# <private_ip_addres> in case of bastion host configuration
c) Restart the rke2-server service
sudo systemctl restart rke2-server.service
d) Check the status of the rke2-server service and make sure it is in running state.
sudo systemctl status rke2-server.service

2. Copy Kubernetes Config file
Copy /etc/rancher/rke2/rke2.yaml in to your local desktop as kube.config
3. Validate Connection from Local Desktop Environment
Edit the server section in kube.config to point to the cluster API server public IP address or its FQDN.
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: <cert-auth-data>
server: https://<public-ip_or_fqdn>::<cluster_port>
name: default
contexts:
- context:
cluster: default
user: default
name: default
current-context: default
kind: Config
preferences: {}
users:
- name: default
user:
client-certificate-data: <client-cert-data>
client-key-data: <client-key-data>
Verify if Kubernetes configuration works.
export KUBECONFIG=$(pwd)/kube.config
kubectl get ns
Use this kube.config file to register the cluster in gopaddle.
4. Register the Cluster in gopaddle
In the gopaddle UI, navigate to the Clusters section
Click on Add a Cluster and select Register an existing Cluster
In the Cluster registration wizard, select the Cluster Access Method as Kube Config
Choose the Cluster Provider type as Other
In the Authentication Step, upload the Kubernetes config file gathered under section "Validate Connection from Local Desktop Environment"

If you have configured a bastion host, provide the Bastion Host IP, SSH Pem file, SSH port

Click on Finish to register the On-premises Cluster.
If you see the error - Network Error ! ServerError: Response not successful: Received status code 503, while view the cluster resources, then check this troubleshooting section for more information.
Last updated