卷

• emptyDir
• hostPath
• gcePersistentDisk
• awsElasticBlockStore
• nfs
• iscsi
• glusterfs
• rbd
• gitRepo
• secret
• persistentVolumeClaim

apiVersion: v1 kind: ReplicationController metadata: name: my-nginx spec: replicas: 1 template: metadata:   labels:     app: nginx spec:   containers:   - name: nginx     image: nginx     ports:     - containerPort: 80   # Mount volume into pod     volumeMounts:       # must match the name of the volume name below       - name: shared-html         # mount path within the container         mountPath: /usr/share/nginx/html # volumes to be mounted to containers   volumes:   - name: shared-html     hostPath:       path: /somepath/shared/html 

Secret

apiVersion: v1 kind: Secret metadata: name: mysecrets data: password: dmFsdWUtMg0K username: someuser 

$ kubectl create -f mysecrecs.yaml 

...     volumeMounts:       # must match the name of the volume name below       - name: my-passwords      readOnly: true         # mount path within the container         mountPath: /etc/my-passwords-volume # volumes to be mounted to containers   volumes:   - name: my-passwords     secrect:       secrectName: mysecrects 

滚动升级

$ kubectl rolling-update my-nginx --image=nginx:1.9.10 Created my-nginx-2088ed66ed908b2434289b30bf3dafe3 Scaling up my-nginx-2088ed66ed908b2434289b30bf3dafe3 from 0 to 3, scalling down Scaling my-nginx-2088ed66ed908b2434289b30bf3dafe3 up to 1 Scaling my-nginx down to 2 Scaling my-nginx-2088ed66ed908b2434289b30bf3dafe3 up to 2 Scaling my-nginx down to 1 Scaling my-nginx-2088ed66ed908b2434289b30bf3dafe3 up to 3 Scaling my-nginx down to 0 Update succeeded. Deleting old controller: my-nginx Renaming my-nginx-2088ed66ed908b2434289b30bf3dafe3 to my-nginx replicationcontroller "my-nginx" rolling updated 

$ kubectl rolling-update my-nginx -f nginxrc-v2.yaml 

Helm

$ mkdir ~/bin $ cd ~/bin $ curl -s https://get.helm.sh | bash 

helm -h 

$ helm update ---> Creating /home/user/.helm/config.yaml ---> Checking repository charts ---> Cloning into '/home/user/.helm/cache/charts'...Already up-to-date. ---> Done 

$ helm search weavescope weavescope - Weave Scope chart 

$ helm info weavescope Name: weavescope Home: http://weave.works/product/scope/ Version: 0.1.1 Description: Weave Scope chart Details: This chart allows to run Weave Scope on Kubernetes 

$ helm fetch weavescope ---> Fetched chart into workspace /home/user/.helm/workspace/charts/weavescope ---> Done 

$ helm install weavescope ---> Running `kubectl create -f` ... service "weave-scope-app" created replicationcontroller "weave-scope-app" created daemonset "weave-scope-probe" created 

---> Done # Weave Scope Using Weave Scope with Kubernetes: https://github.com/weaveworks/scope#using-weave-scope-with-kubernetes If you have a scope.weave.works account and want to run Scope in Cloud Service Mode, comment out the line "$(WEAVE_SCOPE_APP_SERVICE_HOST):$(WEAVE_SCOPE_APP_SERVICE_PORT)"] in scope-probe-ds.yaml manifest and uncomment the line below, replacing "foo" with the Service token which you will obtain when logging in to your scope.weave.works account: "--probe.token=foo"] DaemonSets need to be enabled in Kubernetes cluster and all node hosts are run with the Docker socket at /var/run/docker.sock ========================================
让我们检查复制控制器的工作情况：

$ kubectl get rc weave-scope-app NAME              DESIRED   CURRENT   AGE weave-scope-app   1         1         8m 

完美。现在我们应该检查守护进程集的工作情况了：

$ kubectl get ds weave-scope-probe NAME                DESIRED   CURRENT   NODE-SELECTOR   AGE weave-scope-probe   3         3                   10m 

Weave Scope监听4040端口，但是该个端口并没有暴露给我们。所以让我们建立本地端口到远程端口的跳转，这样我们就可以从自己的笔记本电脑上远程访问它了。

获取Pod列表：

$ kubectl get pods NAME                          READY     STATUS    RESTARTS   AGE weave-scope-app-k8m4k         1/1       Running   0          23m weave-scope-probe-b5jh7       1/1       Running   0          23m weave-scope-probe-psit2       1/1       Running   0          23m 

我们感兴趣的是 weave-scope-app Pod。

我们能像这样增加一个端口跳转：

$ kubectl port-forward weave-scope-app-k8m4k 4040:4040 I0428 18:43:37.014631   14389 portforward.go:213] Forwarding from 127.0.0.1:4040 -> 4040 I0428 18:43:37.015420   14389 portforward.go:213] Forwarding from [::1]:4040 -> 4040 

现在我们开以用浏览器打开 http://127.0.0.1:4040 。

你可以看到WeaveScope的界面：

太棒了。所有的东西都能正常工作了！

如果你过后想要卸载Weave Scope，你可以这样做：

$ helm uninstall weavescope -n default 

总结

相关阅读

• Kubernetes Overview, Part One by Rimantas Mocevicius ON 27 APR 2016
• Connecting Docker Containers, Part Two by Eddy Mavungu ON 4 MAR 2016
• Connecting Docker Containers, Part One by Eddy Mavungu ON 26 FEB 2016
• CoreOS Overview, Part Three by Rimantas Mocevicius ON 12 FEB 2016
• CoreOS Overview, Part Two by Rimantas Mocevicius ON 5 FEB 2016
• etcd on CoreOS by Nitish Tiwari ON 3 FEB 2016