remove mintnet docs
This commit is contained in:
parent
9dc43e0d1c
commit
87724cc451
|
@ -1,15 +0,0 @@
|
||||||
# Setup a Kubernetes cluster on Digital Ocean (DO)
|
|
||||||
|
|
||||||
Available options:
|
|
||||||
|
|
||||||
1. [kubeadm (alpha)](https://kubernetes.io/docs/getting-started-guides/kubeadm/)
|
|
||||||
2. [kargo](https://kubernetes.io/docs/getting-started-guides/kargo/)
|
|
||||||
3. [rancher](http://rancher.com/)
|
|
||||||
4. [terraform](https://github.com/hermanjunge/kubernetes-digitalocean-terraform)
|
|
||||||
|
|
||||||
As you can see, there is no single tool for creating a cluster on DO.
|
|
||||||
Therefore, choose the one you know and comfortable working with. If you know
|
|
||||||
and used [terraform](https://www.terraform.io/) before, then choose it. If you
|
|
||||||
know Ansible, then pick kargo. If none of these seem familiar to you, go with
|
|
||||||
kubeadm. Rancher is a beautiful UI for deploying and managing containers in
|
|
||||||
production.
|
|
|
@ -1,31 +0,0 @@
|
||||||
# Setup a Kubernetes cluster on Google Cloud Engine (GCE)
|
|
||||||
|
|
||||||
Main article: [Running Kubernetes on Google Compute
|
|
||||||
Engine](https://kubernetes.io/docs/getting-started-guides/gce/)
|
|
||||||
|
|
||||||
## 1. Create a cluster
|
|
||||||
|
|
||||||
The recommended way is to use [Google Container
|
|
||||||
Engine](https://cloud.google.com/container-engine/) (GKE). You should be able
|
|
||||||
to create a fully fledged cluster with just a few clicks.
|
|
||||||
|
|
||||||
## 2. Connect to it
|
|
||||||
|
|
||||||
Install `gcloud` as a part of [Google Cloud SDK](https://cloud.google.com/sdk/).
|
|
||||||
|
|
||||||
Make sure you have credentials for GCloud by running `gcloud auth login`.
|
|
||||||
|
|
||||||
In order to make API calls against GCE, you must also run `gcloud auth
|
|
||||||
application-default login`
|
|
||||||
|
|
||||||
Press `Connect` button:
|
|
||||||
|
|
||||||
![Connect button](../img/gce1.png)
|
|
||||||
|
|
||||||
![Connect pop-up](../img/gce2.png)
|
|
||||||
|
|
||||||
and execute the first command in your shell. Then start a proxy by
|
|
||||||
executing `kubectl proxy`.
|
|
||||||
|
|
||||||
Now you should be able to run `kubectl` command to create resources, get
|
|
||||||
resource info, logs, etc.
|
|
Binary file not shown.
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
Before Width: | Height: | Size: 30 KiB |
Loading…
Reference in New Issue