From 77d831c7eaead2ebfe1a9333cf434a30769ffc08 Mon Sep 17 00:00:00 2001 From: Armando Migliaccio Date: Tue, 22 Oct 2019 14:34:13 -0700 Subject: [PATCH] Replace Digital Ocean with DigitalOcean (#17033) The former is the official spelling, but both spellings have been used throughout the docs. This commit replaces the occurrences of the unofficial spelling with the official one. --- .../_posts/2015-07-00-The-Growing-Kubernetes-Ecosystem.md | 2 +- .../blog/_posts/2019-01-17-update-volume-snapshot-alpha.md | 2 +- content/en/docs/concepts/architecture/cloud-controller.md | 2 +- .../tools/kubeadm/troubleshooting-kubeadm.md | 6 +++--- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/blog/_posts/2015-07-00-The-Growing-Kubernetes-Ecosystem.md b/content/en/blog/_posts/2015-07-00-The-Growing-Kubernetes-Ecosystem.md index 7342f621f9..5ba7b58c8e 100644 --- a/content/en/blog/_posts/2015-07-00-The-Growing-Kubernetes-Ecosystem.md +++ b/content/en/blog/_posts/2015-07-00-The-Growing-Kubernetes-Ecosystem.md @@ -95,7 +95,7 @@ Mesosphere has incorporated Kubernetes into its Data Center Operating System (DC | -[Platalytics, Inc][24]. and announced the release of one-touch deploy-anywhere feature for its Spark Application Platform. Based on Kubernetes, Docker, and CoreOS, it allows simple and automated deployment of Apache Hadoop, Spark, and Platalytics platform, with a single click, to all major public clouds, including Google, Amazon, Azure, Digital Ocean, and private on-premise clouds. It also enables hybrid cloud scenarios, where resources on public and private clouds can be mixed. +[Platalytics, Inc][24]. and announced the release of one-touch deploy-anywhere feature for its Spark Application Platform. Based on Kubernetes, Docker, and CoreOS, it allows simple and automated deployment of Apache Hadoop, Spark, and Platalytics platform, with a single click, to all major public clouds, including Google, Amazon, Azure, DigitalOcean, and private on-premise clouds. It also enables hybrid cloud scenarios, where resources on public and private clouds can be mixed. | | diff --git a/content/en/blog/_posts/2019-01-17-update-volume-snapshot-alpha.md b/content/en/blog/_posts/2019-01-17-update-volume-snapshot-alpha.md index 4ffcea965c..b738263e39 100644 --- a/content/en/blog/_posts/2019-01-17-update-volume-snapshot-alpha.md +++ b/content/en/blog/_posts/2019-01-17-update-volume-snapshot-alpha.md @@ -141,7 +141,7 @@ As of the publishing of this blog post, the following CSI drivers support snapsh - [Ceph RBD CSI Driver](https://github.com/ceph/ceph-csi/tree/master/pkg/rbd) - [Portworx CSI Driver](https://github.com/libopenstorage/openstorage/tree/master/csi) - [GlusterFS CSI Driver](https://github.com/gluster/gluster-csi-driver) -- [Digital Ocean CSI Driver](https://github.com/digitalocean/csi-digitalocean) +- [DigitalOcean CSI Driver](https://github.com/digitalocean/csi-digitalocean) - [Ember CSI Driver](https://github.com/embercsi/ember-csi) - [Cinder CSI Driver](https://github.com/kubernetes/cloud-provider-openstack/tree/master/pkg/csi/cinder) - [Datera CSI Driver](https://github.com/Datera/datera-csi) diff --git a/content/en/docs/concepts/architecture/cloud-controller.md b/content/en/docs/concepts/architecture/cloud-controller.md index 8d426aac92..71947e8282 100644 --- a/content/en/docs/concepts/architecture/cloud-controller.md +++ b/content/en/docs/concepts/architecture/cloud-controller.md @@ -227,7 +227,7 @@ The following cloud providers have implemented CCMs: * [AWS](https://github.com/kubernetes/cloud-provider-aws) * [Azure](https://github.com/kubernetes/cloud-provider-azure) * [BaiduCloud](https://github.com/baidu/cloud-provider-baiducloud) -* [Digital Ocean](https://github.com/digitalocean/digitalocean-cloud-controller-manager) +* [DigitalOcean](https://github.com/digitalocean/digitalocean-cloud-controller-manager) * [GCP](https://github.com/kubernetes/cloud-provider-gcp) * [Linode](https://github.com/linode/linode-cloud-controller-manager) * [OpenStack](https://github.com/kubernetes/cloud-provider-openstack) diff --git a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md index d38bdd7e9b..410f36dd0c 100644 --- a/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md +++ b/content/en/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm.md @@ -198,15 +198,15 @@ Error from server: Get https://10.19.0.41:10250/containerLogs/default/mysql-ddc6 ``` - This may be due to Kubernetes using an IP that can not communicate with other IPs on the seemingly same subnet, possibly by policy of the machine provider. -- Digital Ocean assigns a public IP to `eth0` as well as a private one to be used internally as anchor for their floating IP feature, yet `kubelet` will pick the latter as the node's `InternalIP` instead of the public one. +- DigitalOcean assigns a public IP to `eth0` as well as a private one to be used internally as anchor for their floating IP feature, yet `kubelet` will pick the latter as the node's `InternalIP` instead of the public one. - Use `ip addr show` to check for this scenario instead of `ifconfig` because `ifconfig` will not display the offending alias IP address. Alternatively an API endpoint specific to Digital Ocean allows to query for the anchor IP from the droplet: + Use `ip addr show` to check for this scenario instead of `ifconfig` because `ifconfig` will not display the offending alias IP address. Alternatively an API endpoint specific to DigitalOcean allows to query for the anchor IP from the droplet: ```sh curl http://169.254.169.254/metadata/v1/interfaces/public/0/anchor_ipv4/address ``` - The workaround is to tell `kubelet` which IP to use using `--node-ip`. When using Digital Ocean, it can be the public one (assigned to `eth0`) or the private one (assigned to `eth1`) should you want to use the optional private network. The [`KubeletExtraArgs` section of the kubeadm `NodeRegistrationOptions` structure](https://github.com/kubernetes/kubernetes/blob/release-1.13/cmd/kubeadm/app/apis/kubeadm/v1beta1/types.go) can be used for this. + The workaround is to tell `kubelet` which IP to use using `--node-ip`. When using DigitalOcean, it can be the public one (assigned to `eth0`) or the private one (assigned to `eth1`) should you want to use the optional private network. The [`KubeletExtraArgs` section of the kubeadm `NodeRegistrationOptions` structure](https://github.com/kubernetes/kubernetes/blob/release-1.13/cmd/kubeadm/app/apis/kubeadm/v1beta1/types.go) can be used for this. Then restart `kubelet`: