format reference items list
parent
8c3c1ea8e6
commit
df6db4c231
|
@ -170,4 +170,4 @@ spec:
|
|||
|
||||
## 参考
|
||||
|
||||
[Accessing Kubernetes Pods from Outside of the Cluster - alesnosek.com](http://alesnosek.com/blog/2017/02/14/accessing-kubernetes-pods-from-outside-of-the-cluster/)
|
||||
- [Accessing Kubernetes Pods from Outside of the Cluster - alesnosek.com](http://alesnosek.com/blog/2017/02/14/accessing-kubernetes-pods-from-outside-of-the-cluster/)
|
|
@ -94,8 +94,6 @@ spec:
|
|||
|
||||
## 参考
|
||||
|
||||
[资源配额](https://k8smeetup.github.io/docs/concepts/policy/resource-quotas/)
|
||||
|
||||
[为命名空间配置默认的内存请求与限额](https://k8smeetup.github.io/docs/tasks/administer-cluster/memory-default-namespace/)
|
||||
|
||||
[在命名空间中配置默认的CPU请求与限额](https://k8smeetup.github.io/docs/tasks/administer-cluster/cpu-default-namespace/)
|
||||
- [资源配额](https://k8smeetup.github.io/docs/concepts/policy/resource-quotas/)
|
||||
- [为命名空间配置默认的内存请求与限额](https://k8smeetup.github.io/docs/tasks/administer-cluster/memory-default-namespace/)
|
||||
- [在命名空间中配置默认的CPU请求与限额](https://k8smeetup.github.io/docs/tasks/administer-cluster/cpu-default-namespace/)
|
|
@ -322,8 +322,6 @@ spec:
|
|||
|
||||
## 参考
|
||||
|
||||
https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
|
||||
|
||||
[kubernetes contrib - statefulsets](https://github.com/kubernetes/contrib/tree/master/statefulsets)
|
||||
|
||||
http://blog.kubernetes.io/2017/01/running-mongodb-on-kubernetes-with-statefulsets.html
|
||||
- https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
|
||||
- [kubernetes contrib - statefulsets](https://github.com/kubernetes/contrib/tree/master/statefulsets)
|
||||
- http://blog.kubernetes.io/2017/01/running-mongodb-on-kubernetes-with-statefulsets.html
|
|
@ -161,7 +161,7 @@ green open filebeat-docker-test 7xPEwEbUQRirk8oDX36gAA 5 1 2151
|
|||
|
||||
![Kibana页面](../images/filebeat-docker-test.jpg)
|
||||
|
||||
点开没个日志条目,可以看到以下详细字段:
|
||||
点开每个日志条目,可以看到以下详细字段:
|
||||
|
||||
![filebeat收集的日志详细信息](../images/kubernetes-filebeat-detail.png)
|
||||
|
||||
|
@ -170,4 +170,3 @@ green open filebeat-docker-test 7xPEwEbUQRirk8oDX36gAA 5 1 2151
|
|||
- source表示filebeat容器中的日志目录
|
||||
|
||||
我们可以通过人为得使`index` = `service name`,这样就可以方便的收集和查看每个service的日志。
|
||||
|
||||
|
|
|
@ -53,4 +53,4 @@
|
|||
|
||||
## 参考
|
||||
|
||||
[Configuration Best Practices](https://kubernetes.io/docs/concepts/configuration/overview/)
|
||||
- [Configuration Best Practices](https://kubernetes.io/docs/concepts/configuration/overview/)
|
|
@ -134,12 +134,8 @@ $ helm install monocular/monocular
|
|||
|
||||
## 参考
|
||||
|
||||
[Monocular UI]()
|
||||
|
||||
[Helm Chart - GitHub](https://github.com/kubernetes/helm/blob/master/docs/charts.md)
|
||||
|
||||
[简化Kubernetes应用部署工具-Helm之应用部署](https://www.kubernetes.org.cn/2706.html)
|
||||
|
||||
[Speed deployment on Kubernetes with Helm Chart – Quick YAML example from scratch](https://www.ibm.com/blogs/bluemix/2017/10/quick-example-helm-chart-for-kubernetes/)
|
||||
|
||||
[Using a private github repo as helm chart repo (https access)](https://medium.com/@kavehmz/using-a-private-github-repo-as-helm-chart-repo-https-access-95629b2af27c)
|
||||
- [Monocular UI](https://github.com/kubernetes-helm/monocular)
|
||||
- [Helm Chart - GitHub](https://github.com/kubernetes/helm/blob/master/docs/charts.md)
|
||||
- [简化Kubernetes应用部署工具-Helm之应用部署](https://www.kubernetes.org.cn/2706.html)
|
||||
- [Speed deployment on Kubernetes with Helm Chart – Quick YAML example from scratch](https://www.ibm.com/blogs/bluemix/2017/10/quick-example-helm-chart-for-kubernetes/)
|
||||
- [Using a private github repo as helm chart repo (https access)](https://medium.com/@kavehmz/using-a-private-github-repo-as-helm-chart-repo-https-access-95629b2af27c)
|
|
@ -197,4 +197,4 @@ Dashboard 的访问地址不变,重新访问 <http://172.20.0.113:8080/api/v1/
|
|||
|
||||
## 参考
|
||||
|
||||
[WebUI(Dashboard) 文档](https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/)
|
||||
- [WebUI(Dashboard) 文档](https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/)
|
|
@ -392,20 +392,12 @@ Locust模拟10万用户,每秒增长100个。
|
|||
|
||||
## 参考
|
||||
|
||||
[基于 Python 的性能测试工具 locust (与 LR 的简单对比)](https://testerhome.com/topics/4839)
|
||||
|
||||
[Locust docs](http://docs.locust.io/en/latest/what-is-locust.html)
|
||||
|
||||
[python用户负载测试工具:locust](http://timd.cn/2015/09/17/locust/)
|
||||
|
||||
[Kubernetes集群性能测试](https://supereagle.github.io/2017/03/09/kubemark/)
|
||||
|
||||
[CoreOS是如何将Kubernetes的性能提高10倍的](http://dockone.io/article/1050)
|
||||
|
||||
[Kubernetes 1.3 的性能和弹性 —— 2000 节点,60,0000 Pod 的集群](http://blog.fleeto.us/translation/updates-performance-and-scalability-kubernetes-13-2000-node-60000-pod-clusters)
|
||||
|
||||
[运用Kubernetes进行分布式负载测试](http://www.csdn.net/article/2015-07-07/2825155)
|
||||
|
||||
[Kubemark User Guide](https://github.com/kubernetes/community/blob/master/contributors/devel/kubemark-guide.md)
|
||||
|
||||
[Flannel host-gw architecture](https://docs.openshift.com/container-platform/3.4/architecture/additional_concepts/flannel.html)
|
||||
- [基于 Python 的性能测试工具 locust (与 LR 的简单对比)](https://testerhome.com/topics/4839)
|
||||
- [Locust docs](http://docs.locust.io/en/latest/what-is-locust.html)
|
||||
- [python用户负载测试工具:locust](http://timd.cn/2015/09/17/locust/)
|
||||
- [Kubernetes集群性能测试](https://supereagle.github.io/2017/03/09/kubemark/)
|
||||
- [CoreOS是如何将Kubernetes的性能提高10倍的](http://dockone.io/article/1050)
|
||||
- [Kubernetes 1.3 的性能和弹性 —— 2000 节点,60,0000 Pod 的集群](http://blog.fleeto.us/translation/updates-performance-and-scalability-kubernetes-13-2000-node-60000-pod-clusters)
|
||||
- [运用Kubernetes进行分布式负载测试](http://www.csdn.net/article/2015-07-07/2825155)
|
||||
- [Kubemark User Guide](https://github.com/kubernetes/community/blob/master/contributors/devel/kubemark-guide.md)
|
||||
- [Flannel host-gw architecture](https://docs.openshift.com/container-platform/3.4/architecture/additional_concepts/flannel.html)
|
|
@ -173,8 +173,6 @@ helm delete --purge nginx-ingress
|
|||
|
||||
## 参考
|
||||
|
||||
[Ingress-nginx github](https://github.com/kubernetes/ingress-nginx)
|
||||
|
||||
[Nginx chart configuration](https://github.com/kubernetes/charts/tree/master/stable/nginx-ingress)
|
||||
|
||||
[使用Helm管理kubernetes应用](helm.md)
|
||||
- [Ingress-nginx github](https://github.com/kubernetes/ingress-nginx)
|
||||
- [Nginx chart configuration](https://github.com/kubernetes/charts/tree/master/stable/nginx-ingress)
|
||||
- [使用Helm管理kubernetes应用](helm.md)
|
|
@ -234,10 +234,7 @@ replicationcontroller "zeppelin-controller" rolling updated
|
|||
|
||||
## 参考
|
||||
|
||||
[Rolling update机制解析](http://dockone.io/article/328)
|
||||
|
||||
[Running a Stateless Application Using a Deployment](https://kubernetes.io/docs/tasks/run-application/run-stateless-application-deployment/)
|
||||
|
||||
[Simple Rolling Update](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/simple-rolling-update.md)
|
||||
|
||||
[使用kubernetes的deployment进行RollingUpdate](https://segmentfault.com/a/1190000008232770)
|
||||
- [Rolling update机制解析](http://dockone.io/article/328)
|
||||
- [Running a Stateless Application Using a Deployment](https://kubernetes.io/docs/tasks/run-application/run-stateless-application-deployment/)
|
||||
- [Simple Rolling Update](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/simple-rolling-update.md)
|
||||
- [使用kubernetes的deployment进行RollingUpdate](https://segmentfault.com/a/1190000008232770)
|
|
@ -244,8 +244,6 @@ Traefik会解析http请求header里的Host参数将流量转发给Ingress配置
|
|||
|
||||
## 参考
|
||||
|
||||
[Traefik-kubernetes 初试](http://www.colabug.com/thread-1703745-1-1.html)
|
||||
|
||||
[Traefik简介](http://www.tuicool.com/articles/ZnuEfay)
|
||||
|
||||
[Guestbook example](https://github.com/kubernetes/kubernetes/tree/master/examples/guestbook)
|
||||
- [Traefik-kubernetes 初试](http://www.colabug.com/thread-1703745-1-1.html)
|
||||
- [Traefik简介](http://www.tuicool.com/articles/ZnuEfay)
|
||||
- [Guestbook example](https://github.com/kubernetes/kubernetes/tree/master/examples/guestbook)
|
|
@ -128,8 +128,6 @@ curl -sX GET -H "Authorization:bearer `cat /var/run/secrets/kubernetes.io/servic
|
|||
|
||||
## 参考
|
||||
|
||||
[Kubernetes Setup for Prometheus and Grafana](https://github.com/giantswarm/kubernetes-prometheus)
|
||||
|
||||
[RBAC——基于角色的访问控制](../guide/rbac.md)
|
||||
|
||||
[wait-for-endpoints init-containers fails to load with k8s 1.6.0 #56](https://github.com/giantswarm/kubernetes-prometheus/issues/56)
|
||||
- [Kubernetes Setup for Prometheus and Grafana](https://github.com/giantswarm/kubernetes-prometheus)
|
||||
- [RBAC——基于角色的访问控制](../guide/rbac.md)
|
||||
- [wait-for-endpoints init-containers fails to load with k8s 1.6.0 #56](https://github.com/giantswarm/kubernetes-prometheus/issues/56)
|
||||
|
|
|
@ -210,4 +210,4 @@ curl https://raw.githubusercontent.com/rootsongjc/kubernetes-handbook/master/man
|
|||
|
||||
## 参考
|
||||
|
||||
[Getting started - conduit.io](https://conduit.io/getting-started/)
|
||||
- [Getting started - conduit.io](https://conduit.io/getting-started/)
|
|
@ -283,7 +283,5 @@ Hello (172.30.60.14) world (172.30.71.19)!!
|
|||
## 参考
|
||||
|
||||
- https://github.com/linkerd/linkerd-examples
|
||||
|
||||
- [A Service Mesh for Kubernetes](https://cdn2.hubspot.net/hubfs/2818724/A%20Service%20Mesh%20for%20Kubernetes_Final.pdf)
|
||||
|
||||
- [dtab](https://linkerd.io/in-depth/dtabs/)
|
||||
|
|
|
@ -29,4 +29,4 @@
|
|||
|
||||
## 参考
|
||||
|
||||
[谈服务发现的背景、架构以及落地方案](http://www.infoq.com/cn/articles/background-architecture-and-solutions-of-service-discovery)
|
||||
- [谈服务发现的背景、架构以及落地方案](http://www.infoq.com/cn/articles/background-architecture-and-solutions-of-service-discovery)
|
Loading…
Reference in New Issue