Update Digital Ocean variables / docs to use new droplet sizes

This commit is contained in:
irontoby 2018-01-20 20:41:13 -05:00
parent 3dc755994b
commit 50dd3e3b82
2 changed files with 11 additions and 9 deletions

View File

@ -27,8 +27,8 @@ variable "controller_count" {
variable "controller_type" { variable "controller_type" {
type = "string" type = "string"
default = "2gb" default = "s-2vcpu-2gb"
description = "Digital Ocean droplet size (e.g. 2gb (min), 4gb, 8gb)." description = "Digital Ocean droplet size (e.g. s-2vcpu-2gb, s-2vcpu-4gb, s-4vcpu-8gb)."
} }
variable "worker_count" { variable "worker_count" {
@ -39,8 +39,8 @@ variable "worker_count" {
variable "worker_type" { variable "worker_type" {
type = "string" type = "string"
default = "512mb" default = "s-1vcpu-1gb"
description = "Digital Ocean droplet size (e.g. 512mb, 1gb, 2gb, 4gb)" description = "Digital Ocean droplet size (e.g. s-1vcpu-1gb, s-1vcpu-2gb, s-2vcpu-2gb)"
} }
variable "ssh_fingerprints" { variable "ssh_fingerprints" {

View File

@ -106,9 +106,9 @@ module "digital-ocean-nemo" {
cluster_name = "nemo" cluster_name = "nemo"
image = "coreos-stable" image = "coreos-stable"
controller_count = 1 controller_count = 1
controller_type = "2gb" controller_type = "s-2vcpu-2gb"
worker_count = 2 worker_count = 2
worker_type = "512mb" worker_type = "s-1vcpu-1gb"
ssh_fingerprints = ["d7:9d:79:ae:56:32:73:79:95:88:e3:a2:ab:5d:45:e7"] ssh_fingerprints = ["d7:9d:79:ae:56:32:73:79:95:88:e3:a2:ab:5d:45:e7"]
# output assets dir # output assets dir
@ -262,16 +262,18 @@ If you uploaded an SSH key to DigitalOcean (not required), find the fingerprint
|:-----|:------------|:--------|:--------| |:-----|:------------|:--------|:--------|
| image | OS image for droplets | "coreos-stable" | coreos-stable, coreos-beta, coreos-alpha | | image | OS image for droplets | "coreos-stable" | coreos-stable, coreos-beta, coreos-alpha |
| controller_count | Number of controllers (i.e. masters) | 1 | 1 | | controller_count | Number of controllers (i.e. masters) | 1 | 1 |
| controller_type | Digital Ocean droplet size | 2gb | 2gb (min), 4gb, 8gb | | controller_type | Digital Ocean droplet size | s-2vcpu-2gb | s-2vcpu-2gb, s-2vcpu-4gb, s-4vcpu-8gb, ... |
| worker_count | Number of workers | 1 | 3 | | worker_count | Number of workers | 1 | 3 |
| worker_type | Digital Ocean droplet size | 512mb | 512mb, 1gb, 2gb, 4gb | | worker_type | Digital Ocean droplet size | s-1vcpu-1gb | s-1vcpu-1gb, s-1vcpu-2gb, s-2vcpu-2gb, ... |
| networking | Choice of networking provider | "flannel" | "flannel" | | networking | Choice of networking provider | "flannel" | "flannel" |
| pod_cidr | CIDR range to assign to Kubernetes pods | "10.2.0.0/16" | "10.22.0.0/16" | | pod_cidr | CIDR range to assign to Kubernetes pods | "10.2.0.0/16" | "10.22.0.0/16" |
| service_cidr | CIDR range to assign to Kubernetes services | "10.3.0.0/16" | "10.3.0.0/24" | | service_cidr | CIDR range to assign to Kubernetes services | "10.3.0.0/16" | "10.3.0.0/24" |
| cluster_domain_suffix | FQDN suffix for Kubernetes services answered by kube-dns. | "cluster.local" | "k8s.example.com" | | cluster_domain_suffix | FQDN suffix for Kubernetes services answered by kube-dns. | "cluster.local" | "k8s.example.com" |
You can see all valid droplet sizes [on DigitalOcean's website](https://developers.digitalocean.com/documentation/changelog/api-v2/new-size-slugs-for-droplet-plan-changes/) or by [using their `doctl` command-line tool](https://github.com/digitalocean/doctl) via `doctl compute size list`.
!!! warning !!! warning
Do not choose a `controller_type` smaller than `2gb`. The `1gb` droplet is not sufficient for running a controller and bootstrapping will fail. Do not choose a `controller_type` smaller than 2GB. Smaller droplets are not sufficient for running a controller and bootstrapping will fail.
!!! bug !!! bug
Digital Ocean firewalls do not yet support the IP tunneling (IP in IP) protocol used by Calico. You can try using "calico" for `networking`, but it will only work if the cloud firewall is removed (unsafe). Digital Ocean firewalls do not yet support the IP tunneling (IP in IP) protocol used by Calico. You can try using "calico" for `networking`, but it will only work if the cloud firewall is removed (unsafe).