Versions Compared

Old Version 16

changes.mady.by.user Beili Zhou

Saved on

compared with

New Version 17

changes.mady.by.user Mohammadreza Pasandideh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Steps DescriptionKubernetes Node
FirstMasterany otherworker
Install Docker(tick)(tick)
Configure Kubernetes Cluster(tick)(tick)
Install kubectl(tick)(tick)

Install Helm

(expect OOM project will be mounted on the same node)

(tick)(minus)

...

#PurposeCommand and Example
1

Download kubectl on the server

curl -LO https://storage.googleapis.com/kubernetes-release/release/v1.8.6/bin/linux/amd64/kubectl
Expand
titleExample of download kubectl process

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100 49.8M  100 49.8M    0     0  15.3M      0  0:00:03  0:00:03 --:--:-- 15.3M

2

Enable the kubectl command

chmod +x kubectl

sudo mv kubectl /usr/local/bin/kubectl

vi ~/.bashrc

  • append the following to enable kubectl command auto-completion
    • source <(kubectl completion bash)

source ~/.bashrc

3

Generate config from the Rancher UI

From the Rancher UI ( access the Rancher UI through http:<master node host IP>:8880 as specified in Kubernetes Cluster by Rancher),

  • Go to a Kubernetes CLI page through KUBERNETES -> CLI
  • Click on the GenerateConfig button to generate the config

  • The following content will be brought up; click on the Copy to Clipboard button to copy the generated config and use it in next step:

4

Create the kube config on the server

mkdir ~/.kube

vi ~/.kube/config

Paste the generated config from rancher UI (from last step) to this file, then save the file.

5

Validate the kube config

kubectl cluster-info

Expand
titleExample of validation result on kube config through "kubectl cluster-info"

$ kubectl cluster-info

Kubernetes master is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443

Heapster is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443/api/v1/namespaces/kube-system/services/heapster/proxy

KubeDNS is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443/api/v1/namespaces/kube-system/services/kube-dns/proxy

kubernetes-dashboard is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy

monitoring-grafana is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy

monitoring-influxdb is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy

tiller-deploy is running at https://10.147.132.10:8880/r/projects/1a8/kubernetes:6443/api/v1/namespaces/kube-system/services/tiller-deploy/proxy


To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

6

Validate the nodes added

kubectl get nodes

Expand
titleAn example

$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
sdnc-k8s Ready <none> 15m v1.7.7-rancher1
sdnc-k8s-2 Ready <none> 1m v1.7.7-rancher1
$

...