rancher-docs/versioned_docs/version-2.0-2.4/getting-started/quick-start-guides/deploy-rancher-manager/digitalocean.md at 8a7de06bb89d8b4b04b0a4ebfee3b323ffc1ea7a

public/rancher-docs

Fork 0

mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-06 05:03:27 +00:00

Files

T

Billy Tat 986e14346f Fix incorrect filename

2024-01-12 21:20:14 -08:00

3.4 KiB

Raw Blame History

title, description

title	description
Rancher DigitalOcean Quick Start Guide	Read this step by step Rancher DigitalOcean guide to quickly deploy a Rancher Server with a single node cluster attached.

The following steps will quickly deploy a Rancher Server on DigitalOcean with a single node cluster attached.

Note: The intent of these guides is to quickly launch a sandbox that you can use to evaluate Rancher. These guides are not intended for production environments. For comprehensive setup instructions, see Installation.

Prerequisites

Note

Deploying to DigitalOcean will incur charges.

DigitalOcean Account: You will require an account on DigitalOcean as this is where the server and cluster will run.
DigitalOcean Access Key: Use this link to create a DigitalOcean Access Key if you don't have one.
Terraform: Used to provision the server and cluster to DigitalOcean.

Getting Started

Clone Rancher Quickstart to a folder using git clone https://github.com/rancher/quickstart.
Go into the DigitalOcean folder containing the Terraform files by executing cd quickstart/do.
Rename the terraform.tfvars.example file to terraform.tfvars.
Edit terraform.tfvars and customize the following variables:
- do_token - DigitalOcean access key
- rancher_server_admin_password - Admin password for created Rancher server
Optional: Modify optional variables within terraform.tfvars. See the Quickstart Readme and the DO Quickstart Readme for more information. Suggestions include:
- do_region - DigitalOcean region, choose the closest instead of the default
- prefix - Prefix for all created resources
- droplet_size - Droplet size used, minimum is s-2vcpu-4gb but s-4vcpu-8gb could be used if within budget
- ssh_key_file_name - Use a specific SSH key instead of ~/.ssh/id_rsa (public key is assumed to be ${ssh_key_file_name}.pub)
Run terraform init.

To initiate the creation of the environment, run terraform apply --auto-approve. Then wait for output similar to the following:

Apply complete! Resources: 15 added, 0 changed, 0 destroyed.

Outputs:

rancher_node_ip = xx.xx.xx.xx
rancher_server_url = https://rancher.xx.xx.xx.xx.sslip.io
workload_node_ip = yy.yy.yy.yy

Paste the rancher_server_url from the output above into the browser. Log in when prompted (default username is admin, use the password set in rancher_server_admin_password).

Result

Two Kubernetes clusters are deployed into your DigitalOcean account, one running Rancher Server and the other ready for experimentation deployments.

What's Next?

Use Rancher to create a deployment. For more information, see Creating Deployments.

Destroying the Environment

From the quickstart/do folder, execute terraform destroy --auto-approve.
Wait for confirmation that all resources have been destroyed.

3.4 KiB Raw Blame History