Rancher Manager deployment

1. From the Morpheus portal access the “Provisioning”→”Instances”
   
   
   
   
2. Press “Add” to start the Rancher Instance creation
   
   
   
3. Search for Rancher in the search bar and select the Rancher Manager instance type and press “Next”:
   
   
   
4. Fill in the basic parameters like “Name” :
   
   
   
   
5. Keep filling the instance configuration parameters :
   - Plan (e.g. 8cpu-8gbmem-30gbdisk).
   - Networks (the instance requires a public IP, this could be achieved either attaching the private network and use a floating-ip or by attaching directly the "external-internet" network ; more information can be found in the page Provision a new instance - web).
   - Rancher Dashboard Admin Password: this is the password needed to access the Rancher Dashboard at the end of the provisioning (username: "admin") - the password shall be saved and will also be needed for the provisioning and connection of the kubernetes clusters.
   - Security Group : "ssh-https"
   
   
   
6. Continue with the default setting in the next panels and after reviewing the settings press "Complete" to start the provisioning:
   
   
   
7. Wait for the deployment to complete, it should take on average between 15-20 minutes:
   
   
   
8. Once the deployment is completed it is possible to access the created instance by connecting via a browser to the following url: "https://<rancher instance name>.<tenancy name>.<site char>.ewcloud.host"  according to the naming convention explained on the page EWC DNS
   
   

RKE2 cluster deployment

1.  From the Morpheus portal access the “Provisioning”→”Instances” , access the "Rancher" instance page and go under "Actions"→"Run workflow" :
   
   
   
2. Search for the workflow "Deploy RKE2 cluster" :
   
   
   
3. Fill in the necessary parameters:
   - Rancher Dashboard Admin Password :  this the password that was set to access the Rancher Dashboard instance
   - RKE2 Cluster Name: name for the cluster that will appear on the dashboard
   - RKE2 Cluster Environment: tag for the cluster (dev, stage, prod)
   - RKE2 Cluster Kubernetes version: version of the kubernetes cluster (e.g. 1.28)
   - RKE2 Cluster worker node plan: resources plan for the worker node (e.g. 8cpu-8gbmem-30gbdisk)
   - RKE2 Cluster Kubernetes deployment mode: "Development" (1 controller node) or "High Availability" (3 controller nodes)
   - RKE2 Cluster Autoscaler maximum number of nodes: upper limit for scaling up the size of the cluster (minimum is set to 2 worker nodes)
   - Leave empty the "Command Options" field
   
   Once filled the parameters press "Execute" :
   
   
   
4. Monitor the execution of the workflow via the progress bar and the "History" tab for more information:
   
   
   
   
5. Wait for the workflow to finalize and once completed the new cluster should be connected and visible in the Rancher Dashboard:
   
   
   
   
6. If required, multiple clusters could be provisioned and connected to the Rancher Dashboard, in this case it is enough o re-execute the workflow to deploy the additional clusters.