symbol errors in quotation mark

Signed-off-by: tim-zju <21651152@zju.edu.cn>
2016-12-22 15:12:07 +08:00
parent b27310d81a 5be27c3194
commit 30f1d03b8d
49 changed files with 779 additions and 129 deletions
@@ -78,9 +78,10 @@ KUBE_ALLOW_PRIV="--allow-privileged=false"
 KUBE_MASTER="--master=http://centos-master:8080"
 ```

-* Disable the firewall on the master and all the nodes, as docker does not play well with other firewall rule managers
+* Disable the firewall on the master and all the nodes, as docker does not play well with other firewall rule managers. CentOS won't let you disable the firewall as long as SELinux is enforcing, so that needs to be disabled first.

 ```shell
+setenforce 0
 systemctl disable iptables-services firewalld
 systemctl stop iptables-services firewalld
 ```
@@ -118,10 +119,11 @@ KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
 KUBE_API_ARGS=""
 ```

-* Configure ETCD to hold the network overlay configuration on master:
+* Start ETCD and configure it to hold the network overlay configuration on master:
 **Warning** This network must be unused in your network infrastructure! `172.30.0.0/16` is free in our network.

 ```shell
+$ systemctl start etcd
 $ etcdctl mkdir /kube-centos/network
 $ etcdctl mk /kube-centos/network/config "{ \"Network\": \"172.30.0.0/16\", \"SubnetLen\": 24, \"Backend\": { \"Type\": \"vxlan\" } }"
 ```
@@ -164,7 +166,8 @@ KUBELET_ADDRESS="--address=0.0.0.0"
 KUBELET_PORT="--port=10250"

 # You may leave this blank to use the actual hostname
-KUBELET_HOSTNAME="--hostname-override=centos-minion-n" # Check the node number!
+# Check the node number!
+KUBELET_HOSTNAME="--hostname-override=centos-minion-n"

 # Location of the api-server
 KUBELET_API_SERVER="--api-servers=http://centos-master:8080"
@@ -228,4 +231,3 @@ IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs
 Bare-metal           | custom       | CentOS | flannel     | [docs](/docs/getting-started-guides/centos/centos_manual_config)            |          | Community ([@coolsvap](https://github.com/coolsvap))

 For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart.
-
@@ -37,7 +37,7 @@ master,etcd = kube-master.example.com
 If not

 ```shell
-yum install -y ansible git python-netaddr
+dnf install -y ansible git python-netaddr
 ```

 **Now clone down the Kubernetes repository**
@@ -11,7 +11,7 @@ title: Fedora (Single Node)

 ## Prerequisites

-1. You need 2 or more machines with Fedora installed.
+1. You need 2 or more machines with Fedora installed. These can be either bare metal machines or virtual machines.

 ## Instructions

@@ -33,18 +33,16 @@ fed-node = 192.168.121.65
 **Prepare the hosts:**

 * Install Kubernetes on all hosts - fed-{master,node}.  This will also pull in docker. Also install etcd on fed-master.  This guide has been tested with kubernetes-0.18 and beyond.
-* The [--enablerepo=updates-testing](https://fedoraproject.org/wiki/QA:Updates_Testing) directive in the yum command below will ensure that the most recent Kubernetes version that is scheduled for pre-release will be installed. This should be a more recent version than the Fedora "stable" release for Kubernetes that you would get without adding the directive.
-* If you want the very latest Kubernetes release [you can download and yum install the RPM directly from Fedora Koji](http://koji.fedoraproject.org/koji/packageinfo?packageID=19202) instead of using the yum install command below.
 * Running on AWS EC2 with RHEL 7.2, you need to enable "extras" repository for yum by editing `/etc/yum.repos.d/redhat-rhui.repo` and changing the changing the `enable=0` to `enable=1` for extras.

 ```shell
-yum -y install --enablerepo=updates-testing kubernetes
+dnf -y install kubernetes
 ```

-* Install etcd and iptables
+* Install etcd

 ```shell
-yum -y install etcd iptables
+dnf -y install etcd
 ```

 * Add master and node to /etc/hosts on all machines (not needed if hostnames already in DNS). Make sure that communication works between fed-master and fed-node by using a utility such as ping.
@@ -54,20 +52,12 @@ echo "192.168.121.9	fed-master
 192.168.121.65	fed-node" >> /etc/hosts
 ```

-* Edit /etc/kubernetes/config which will be the same on all hosts (master and node) to contain:
+* Edit /etc/kubernetes/config (which should be the same on all hosts) to set
+the name of the master server:

 ```shell
 # Comma separated list of nodes in the etcd cluster
 KUBE_MASTER="--master=http://fed-master:8080"
-
-# logging to stderr means we get it in the systemd journal
-KUBE_LOGTOSTDERR="--logtostderr=true"
-
-# journal message level, 0 is debug
-KUBE_LOG_LEVEL="--v=0"
-
-# Should this cluster be allowed to run privileged docker containers
-KUBE_ALLOW_PRIV="--allow-privileged=false"
 ```

 * Disable the firewall on both the master and node, as docker does not play well with other firewall rule managers.  Please note that iptables-services does not exist on default fedora server install.
@@ -86,7 +76,7 @@ systemctl stop iptables-services firewalld
 KUBE_API_ADDRESS="--address=0.0.0.0"

 # Comma separated list of nodes in the etcd cluster
-KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:4001"
+KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:2379"

 # Address range to use for services
 KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
@@ -95,18 +85,10 @@ KUBE_SERVICE_ADDRESSES="--service-cluster-ip-range=10.254.0.0/16"
 KUBE_API_ARGS=""
 ```

-* Edit /etc/etcd/etcd.conf,let the etcd to listen all the ip instead of 127.0.0.1, if not, you will get the error like "connection refused". Note that Fedora 22 uses etcd 2.0, One of the changes in etcd 2.0 is that now uses port 2379 and 2380 (as opposed to etcd 0.46 which userd 4001 and 7001).
+* Edit /etc/etcd/etcd.conf to let etcd listen on all available IPs instead of 127.0.0.1; If you have not done this, you might see an error such as "connection refused".

 ```shell
-ETCD_LISTEN_CLIENT_URLS="http://0.0.0.0:4001"
-```
-
-* Create /var/run/kubernetes on master:
-
-```shell
-mkdir /var/run/kubernetes
-chown kube:kube /var/run/kubernetes
-chmod 750 /var/run/kubernetes
+ETCD_LISTEN_CLIENT_URLS="http://0.0.0.0:2379"
 ```

 * Start the appropriate services on master:
@@ -50,13 +50,19 @@ etcdctl get /coreos.com/network/config

 **Perform following commands on all Kubernetes nodes**

+Install the flannel package
+
+```shell
+# dnf -y install flannel
+```
+
 Edit the flannel configuration file /etc/sysconfig/flanneld as follows:

 ```shell
 # Flanneld configuration options

 # etcd url location.  Point this to the server where etcd runs
-FLANNEL_ETCD="http://fed-master:4001"
+FLANNEL_ETCD="http://fed-master:2379"

 # etcd config key.  This is the configuration key that flannel queries
 # For address range assignment
@@ -105,7 +111,7 @@ Now check the interfaces on the nodes. Notice there is now a flannel.1 interface
 From any node in the cluster, check the cluster members by issuing a query to etcd server via curl (only partial output is shown using `grep -E "\{|\}|key|value"`). If you set up a 1 master and 3 nodes cluster, you should see one block for each node showing the subnets they have been assigned. You can associate those subnets to each node by the MAC address (VtepMAC) and IP address (Public IP) that is listed in the output.

 ```shell
-curl -s http://fed-master:4001/v2/keys/coreos.com/network/subnets | python -mjson.tool
+curl -s http://fed-master:2379/v2/keys/coreos.com/network/subnets | python -mjson.tool
 ```

 ```json
@@ -149,7 +155,7 @@ bash-4.3#
 This will place you inside the container. Install iproute and iputils packages to install ip and ping utilities. Due to a [bug](https://bugzilla.redhat.com/show_bug.cgi?id=1142311), it is required to modify capabilities of ping binary to work around "Operation not permitted" error.

 ```shell
-bash-4.3# yum -y install iproute iputils
+bash-4.3# dnf -y install iproute iputils
 bash-4.3# setcap cap_net_raw-ep /usr/bin/ping
 ```

@@ -60,6 +60,7 @@ few commands, and have active community support.
 - [Azure](/docs/getting-started-guides/azure)
 - [CenturyLink Cloud](/docs/getting-started-guides/clc)
 - [IBM SoftLayer](https://github.com/patrocinio/kubernetes-softlayer)
+- [Stackpoint.io](/docs/getting-started-guides/stackpoint/)

 ### Custom Solutions

@@ -19,7 +19,7 @@ The installation uses a tool called `kubeadm` which is part of Kubernetes.
 This process works with local VMs, physical servers and/or cloud servers.
 It is simple enough that you can easily integrate its use into your own automation (Terraform, Chef, Puppet, etc).

-See the full [`kubeadm` reference](/docs/admin/kubeadm) for information on all `kubeadm` command-line flags and for advice on automating `kubeadm` itself.
+See the full `kubeadm` [reference](/docs/admin/kubeadm) for information on all `kubeadm` command-line flags and for advice on automating `kubeadm` itself.

 **The `kubeadm` tool is currently in alpha but please try it out and give us [feedback](/docs/getting-started-guides/kubeadm/#feedback)!
 Be sure to read the [limitations](#limitations); in particular note that kubeadm doesn't have great support for
@@ -69,18 +69,18 @@ For each host in turn:
 * SSH into the machine and become `root` if you are not already (for example, run `sudo su -`).
 * If the machine is running Ubuntu or HypriotOS, run:

-      # curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
-      # cat <<EOF > /etc/apt/sources.list.d/kubernetes.list
+      curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
+      cat <<EOF > /etc/apt/sources.list.d/kubernetes.list
      deb http://apt.kubernetes.io/ kubernetes-xenial main
      EOF
-      # apt-get update
-      # # Install docker if you don't have it already.
-      # apt-get install -y docker.io
-      # apt-get install -y kubelet kubeadm kubectl kubernetes-cni
+      apt-get update
+      # Install docker if you don't have it already.
+      apt-get install -y docker.io
+      apt-get install -y kubelet kubeadm kubectl kubernetes-cni

   If the machine is running CentOS, run:

-      # cat <<EOF > /etc/yum.repos.d/kubernetes.repo
+      cat <<EOF > /etc/yum.repos.d/kubernetes.repo
      [kubernetes]
      name=Kubernetes
      baseurl=http://yum.kubernetes.io/repos/kubernetes-el7-x86_64
@@ -90,10 +90,10 @@ For each host in turn:
      gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
             https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
      EOF
-      # setenforce 0
-      # yum install -y docker kubelet kubeadm kubectl kubernetes-cni
-      # systemctl enable docker && systemctl start docker
-      # systemctl enable kubelet && systemctl start kubelet
+      setenforce 0
+      yum install -y docker kubelet kubeadm kubectl kubernetes-cni
+      systemctl enable docker && systemctl start docker
+      systemctl enable kubelet && systemctl start kubelet

 The kubelet is now restarting every few seconds, as it waits in a crashloop for `kubeadm` to tell it what to do.

@@ -116,7 +116,7 @@ plugins, if required.

 ### Reusing the Docker daemon

-When using a single VM of kubernetes its really handy to reuse the Docker daemon inside the VM; as this means you don't have to build on your host machine and push the image into a docker registry - you can just build inside the same docker daemon as minikube which speeds up local experiments.
+When using a single VM of kubernetes, it's really handy to reuse the minikube's built-in Docker daemon; as this means you don't have to build a docker registry on your host machine and push the image into it - you can just build inside the same docker daemon as minikube which speeds up local experiments. Just make sure you tag your Docker image with something other than 'latest' and use that tag while you pull the image. Otherwise, if you do not specify version of your image, it will be assumed as `:latest`, with pull image policy of `Always` correspondingly, which may eventually result in `ErrImagePull` as you may not have any versions of your Docker image out there in the default docker registry (usually DockerHub) yet.

 To be able to work with the docker daemon on your mac/linux host use the [docker-env command](./docs/minikube_docker-env.md) in your shell:

@@ -646,7 +646,7 @@ This pod mounts several node file system directories using the  `hostPath` volum

 Apiserver supports several cloud providers.

- options for `--cloud-provider` flag are `aws`, `gce`, `mesos`, `openshift`, `ovirt`, `rackspace`, `vagrant`, or unset.
+- options for `--cloud-provider` flag are `aws`, `azure`, `cloudstack`, `fake`, `gce`, `mesos`, `openstack`, `ovirt`, `photon`, `rackspace`, `vsphere`, or unset.
 - unset used for e.g. bare metal setups.
 - support for new IaaS is added by contributing code [here](https://releases.k8s.io/{{page.githubbranch}}/pkg/cloudprovider/providers)

@@ -0,0 +1,203 @@
+---
+assignees:
+- baldwinspc
+
+---
+
+* TOC
+{:toc}
+
+
+## Introduction
+
+StackPointCloud is the universal control plane for Kubernetes Anywhere.  StackPointCloud allows you to deploy and manage a Kubernetes cluster to the cloud provider of your choice in 3 steps using a web-based interface.
+
+## AWS
+
+To create a Kubernetes cluster on AWS, you will need an Access Key ID and a Secret Access Key from AWS.
+
+### Choose a Provider
+
+Log in to [stackpoint.io](https://stackpoint.io) with a GitHub, Google, or Twitter account.
+
+Click **+ADD A CLUSTER NOW**.
+
+Click to select Amazon Web Services (AWS).
+
+### Configure Your Provider
+
+Add your Access Key ID and a Secret Access Key from AWS. Select your default StackPointCloud SSH keypair, or click **ADD SSH KEY** to add a new keypair.
+
+Click **SUBMIT** to submit the authorization information.
+
+### Configure Your Cluster
+
+Choose any extra options you may want to include with your cluster, then click **SUBMIT** to create the cluster. 
+
+### Running the Cluster
+
+You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters).
+
+For information on using and managing a Kubernetes cluster on AWS, [consult the  Kubernetes documentation](http://kubernetes.io/docs/getting-started-guides/aws/).
+
+
+
+
+## GCE
+
+To create a Kubernetes cluster on GCE, you will need the Service Account JSON Data from Google.
+
+
+### Choose a Provider
+
+Log in to [stackpoint.io](https://stackpoint.io) with a GitHub, Google, or Twitter account.
+
+Click **+ADD A CLUSTER NOW**.
+
+Click to select Google Compute Engine (GCE).
+
+### Configure Your Provider
+
+Add your Service Account JSON Data from Google. Select your default StackPointCloud SSH keypair, or click **ADD SSH KEY** to add a new keypair.
+
+Click **SUBMIT** to submit the authorization information.
+
+### Configure Your Cluster
+
+Choose any extra options you may want to include with your cluster, then click **SUBMIT** to create the cluster. 
+
+### Running the Cluster
+
+You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters).
+
+For information on using and managing a Kubernetes cluster on GCE, [consult the  Kubernetes documentation](http://kubernetes.io/docs/getting-started-guides/gce).
+
+
+
+
+
+## GKE
+
+To create a Kubernetes cluster on GKE, you will need the Service Account JSON Data from Google.
+
+### Choose a Provider
+
+Log in to [stackpoint.io](https://stackpoint.io) with a GitHub, Google, or Twitter account.
+
+Click **+ADD A CLUSTER NOW**.
+
+Click to select Google Container Engine (GKE).
+
+### Configure Your Provider
+
+Add your Service Account JSON Data from Google. Select your default StackPointCloud SSH keypair, or click **ADD SSH KEY** to add a new keypair.
+
+Click **SUBMIT** to submit the authorization information.
+
+### Configure Your Cluster
+
+Choose any extra options you may want to include with your cluster, then click **SUBMIT** to create the cluster. 
+
+
+### Running the Cluster
+
+You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters).
+
+For information on using and managing a Kubernetes cluster on GKE, consult [the official documentation](http://kubernetes.io/docs/).
+
+
+
+
+
+## DigitalOcean
+
+To create a Kubernetes cluster on DigitalOcean, you will need a DigitalOcean API Token.
+
+### Choose a Provider
+
+Log in to [stackpoint.io](https://stackpoint.io) with a GitHub, Google, or Twitter account.
+
+Click **+ADD A CLUSTER NOW**.
+
+Click to select DigitalOcean.
+
+### Configure Your Provider
+
+Add your DigitalOcean API Token. Select your default StackPointCloud SSH keypair, or click **ADD SSH KEY** to add a new keypair.
+
+Click **SUBMIT** to submit the authorization information.
+
+### Configure Your Cluster
+
+Choose any extra options you may want to include with your cluster, then click **SUBMIT** to create the cluster. 
+
+### Running the Cluster
+
+You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters).
+
+For information on using and managing a Kubernetes cluster on DigitalOcean, consult [the official documentation](http://kubernetes.io/docs/).
+
+
+
+
+
+## Microsoft Azure
+
+To create a Kubernetes cluster on Microsoft Azure, you will need an Azure Subscription ID, Username/Email, and Password.
+
+### Choose a Provider
+
+Log in to [stackpoint.io](https://stackpoint.io) with a GitHub, Google, or Twitter account.
+
+Click **+ADD A CLUSTER NOW**.
+
+Click to select Microsoft Azure.
+
+### Configure Your Provider
+
+Add your Azure Subscription ID, Username/Email, and Password. Select your default StackPointCloud SSH keypair, or click **ADD SSH KEY** to add a new keypair.
+
+Click **SUBMIT** to submit the authorization information.
+
+### Configure Your Cluster
+
+Choose any extra options you may want to include with your cluster, then click **SUBMIT** to create the cluster. 
+
+
+### Running the Cluster
+
+You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters).
+
+For information on using and managing a Kubernetes cluster on Azure, [consult the  Kubernetes documentation](http://kubernetes.io/docs/getting-started-guides/azure/).
+
+
+
+
+
+## Packet
+
+To create a Kubernetes cluster on Packet, you will need a Packet API Key.
+
+### Choose a Provider
+
+Log in to [stackpoint.io](https://stackpoint.io) with a GitHub, Google, or Twitter account.
+
+Click **+ADD A CLUSTER NOW**.
+
+Click to select Packet.
+
+### Configure Your Provider
+
+Add your Packet API Key. Select your default StackPointCloud SSH keypair, or click **ADD SSH KEY** to add a new keypair.
+
+Click **SUBMIT** to submit the authorization information.
+
+### Configure Your Cluster
+
+Choose any extra options you may want to include with your cluster, then click **SUBMIT** to create the cluster. 
+
+### Running the Cluster
+
+You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters).
+
+For information on using and managing a Kubernetes cluster on Packet, consult [the official documentation](http://kubernetes.io/docs/).
@@ -12,7 +12,7 @@ In Kubernetes version 1.5, Windows Server Containers for Kubernetes is supported
 1. Kubernetes control plane running on existing Linux infrastructure (version 1.5 or later)
 2. Kubenet network plugin setup on the Linux nodes
 3. Windows Server 2016 (RTM version 10.0.14393 or later)
-4. Docker Version 1.12.2-cs2-ws-beta or later
+4. Docker Version 1.12.2-cs2-ws-beta or later for Windows Server nodes (Linux nodes and Kubernetes control plane can run any Kubernetes supported Docker Version)

 ## Networking
 Network is achieved using L3 routing. Because third-party networking plugins (e.g. flannel, calico, etc) don't natively work on Windows Server, existing technology that is built into the Windows and Linux operating systems is relied on. In this L3 networking approach, a /16 subnet is chosen for the cluster nodes, and a /24 subnet is assigned to each worker node. All pods on a given worker node will be connected to the /24 subnet. This allows pods on the same node to communicate with each other. In order to enable networking between pods running on different nodes, routing features that are built into Windows Server 2016 and Linux are used.
@@ -40,6 +40,7 @@ To run Windows Server Containers on Kubernetes, you'll need to set up both your
 2. DNS support for Windows recently got merged to docker master and is currently not supported in a stable docker release. To use DNS build docker from master or download the binary from [Docker master](https://master.dockerproject.org/)
 3. Pull the `apprenda/pause` image from `https://hub.docker.com/r/apprenda/pause`
 4. RRAS (Routing) Windows feature enabled
+5. Install a VMSwitch of type `Internal`, by running `New-VMSwitch -Name KubeProxySwitch -SwitchType Internal` command in *PowerShell* window. This will create a new Network Interface with name `vEthernet (KubeProxySwitch)`. This interface will be used by kube-proxy to add Service IPs.

 **Linux Host Setup**

@@ -127,14 +128,14 @@ To start kube-proxy on your Windows node:

 Run the following in a PowerShell window with administrative privileges. Be aware that if the node reboots or the process exits, you will have to rerun the commands below to restart the kube-proxy.

-1. Set environment variable *INTERFACE_TO_ADD_SERVICE_IP* value to a node only network interface. The interface created when docker is installed should work
-`$env:INTERFACE_TO_ADD_SERVICE_IP = "vEthernet (HNS Internal NIC)"`
+1. Set environment variable *INTERFACE_TO_ADD_SERVICE_IP* value to `vEthernet (KubeProxySwitch)` which we created in **_Windows Host Setup_** above
+`$env:INTERFACE_TO_ADD_SERVICE_IP = "vEthernet (KubeProxySwitch)"`

 2. Run *kube-proxy* executable using the below command
 `.\proxy.exe --v=3 --proxy-mode=userspace --hostname-override=<ip address/hostname of the windows node> --master=<api server location> --bind-address=<ip address of the windows node>`

 ## Scheduling Pods on Windows
-Because your cluster has both Linux and Windows nodes, you must explictly set the nodeSelector constraint to be able to schedule Pods to Windows nodes. You must set nodeSelector with the label beta.kubernetes.io/os to the value windows; see the following example:
+Because your cluster has both Linux and Windows nodes, you must explicitly set the nodeSelector constraint to be able to schedule Pods to Windows nodes. You must set nodeSelector with the label beta.kubernetes.io/os to the value windows; see the following example:

 ```
 {