修改链接和错字
parent
44b1eaf244
commit
0b1fde236d
|
@ -5,31 +5,31 @@
|
|||
|
||||
## 环境配置
|
||||
|
||||
[Docker1.13环境配置](https://rootsongjc.github.io/docker-practice/docs/docker_env)
|
||||
[Docker1.13环境配置](https://jimmysong.io/docker-practice/docs/docker_env)
|
||||
|
||||
[docker源码编译](https://rootsongjc.github.io/docker-practice/docs/docker_compile)
|
||||
[docker源码编译](https://jimmysong.io/docker-practice/docs/docker_compile)
|
||||
|
||||
|
||||
## 网络管理
|
||||
|
||||
网络配置和管理是容器使用中的的一个重点和难点,对比我们之前使用的docker版本是1.11.1,docker1.13中网络模式跟之前的变动比较大,我们会花大力气讲解。
|
||||
|
||||
[如何创建docker network](https://rootsongjc.github.io/docker-practice/docs/create_network)
|
||||
[如何创建docker network](https://jimmysong.io/docker-practice/docs/create_network)
|
||||
|
||||
[Rancher网络探讨和扁平网络实现](https://rootsongjc.github.io/docker-practice/docs/rancher_network)
|
||||
[Rancher网络探讨和扁平网络实现](https://jimmysong.io/docker-practice/docs/rancher_network)
|
||||
|
||||
[swarm mode的路由网络](https://rootsongjc.github.io/docker-practice/docs/swarm_mode_routing_mesh)
|
||||
[swarm mode的路由网络](https://jimmysong.io/docker-practice/docs/swarm_mode_routing_mesh)
|
||||
|
||||
[docker扁平化网络插件Shrike(基于docker1.11)](https://github.com/TalkingData/shrike)
|
||||
|
||||
## 存储管理
|
||||
|
||||
[Docker存储插件](https://rootsongjc.github.io/docker-practice/docs/docker_storage_plugin)
|
||||
[Docker存储插件](https://jimmysong.io/docker-practice/docs/docker_storage_plugin)
|
||||
|
||||
- [infinit](https://rootsongjc.github.io/docker-practice/docs/infinit) 被docker公司收购的法国团队开发
|
||||
- [convoy](https://rootsongjc.github.io/docker-practice/docs/convoy) rancher开发的docker volume plugin
|
||||
- [torus](https://rootsongjc.github.io/docker-practice/docs/torus) **已废弃**
|
||||
- [flocker](https://rootsongjc.github.io/docker-practice/docs/flocker) ClusterHQ开发
|
||||
- [infinit](https://jimmysong.io/docker-practice/docs/infinit) 被docker公司收购的法国团队开发
|
||||
- [convoy](https://jimmysong.io/docker-practice/docs/convoy) rancher开发的docker volume plugin
|
||||
- [torus](https://jimmysong.io/docker-practice/docs/torus) **已废弃**
|
||||
- [flocker](https://jimmysong.io/docker-practice/docs/flocker) ClusterHQ开发
|
||||
|
||||
|
||||
|
||||
|
@ -39,40 +39,38 @@ Docker提供了一系列[log drivers](https://docs.docker.com/engine/admin/loggi
|
|||
|
||||
需要配置docker engine的启动参数。
|
||||
|
||||
[docker logging driver](https://rootsongjc.github.io/docker-practice/docs/docker_logging_driver)
|
||||
|
||||
## 创建应用
|
||||
|
||||
官方文档:[Docker swarm sample app overview](https://docs.docker.com/engine/getstarted-voting-app/)
|
||||
|
||||
[基于docker1.13手把手教你创建swarm app](https://rootsongjc.github.io/docker-practice/docs/create_swarm_app)
|
||||
[基于docker1.13手把手教你创建swarm app](https://jimmysong.io/docker-practice/docs/create_swarm_app)
|
||||
|
||||
[swarm集群应用管理](https://rootsongjc.github.io/docker-practice/docs/swarm_app_manage)
|
||||
[swarm集群应用管理](https://jimmysong.io/docker-practice/docs/swarm_app_manage)
|
||||
|
||||
[使用docker-compose创建应用](https://rootsongjc.github.io/docker-practice/docs/docker_compose)
|
||||
[使用docker-compose创建应用](https://jimmysong.io/docker-practice/docs/docker_compose)
|
||||
|
||||
## 集群管理##
|
||||
|
||||
我们使用docker内置的swarm来管理docker集群。
|
||||
|
||||
[swarm mode介绍](https://rootsongjc.github.io/docker-practice/docs/swarm_mode)
|
||||
[swarm mode介绍](https://jimmysong.io/docker-practice/docs/swarm_mode)
|
||||
|
||||
我们推荐使用开源的docker集群管理配置方案:
|
||||
|
||||
- [Crane](https://github.com/Dataman-Cloud/crane):由数人云开源的基于swarmkit的容器管理软件,可以作为docker和go语言开发的一个不错入门项目
|
||||
- [Rancher](https://github.com/rancher/rancher):Rancher是一个企业级的容器管理平台,可以使用Kubernetes、swarm和rancher自研的cattle来管理集群。
|
||||
|
||||
[Crane的部署和使用](https://rootsongjc.github.io/docker-practice/docs/crane_usage)
|
||||
[Crane的部署和使用](https://jimmysong.io/docker-practice/docs/crane_usage)
|
||||
|
||||
[Rancher的部署和使用](https://rootsongjc.github.io/docker-practice/docs/rancher_usage)
|
||||
[Rancher的部署和使用](https://jimmysong.io/docker-practice/docs/rancher_usage)
|
||||
|
||||
## 资源限制
|
||||
|
||||
[内存资源限制](https://rootsongjc.github.io/docker-practice/docs/memory_resource_limit)
|
||||
[内存资源限制](https://jimmysong.io/docker-practice/docs/memory_resource_limit)
|
||||
|
||||
[CPU资源限制](https://rootsongjc.github.io/docker-practice/docs/cpu_resource_limit)
|
||||
[CPU资源限制](https://jimmysong.io/docker-practice/docs/cpu_resource_limit)
|
||||
|
||||
[IO资源限制](https://rootsongjc.github.io/docker-practice/docs/io_resource_limit)
|
||||
[IO资源限制](https://jimmysong.io/docker-practice/docs/io_resource_limit)
|
||||
|
||||
## 服务发现
|
||||
|
||||
|
@ -92,47 +90,47 @@ Docker提供了一系列[log drivers](https://docs.docker.com/engine/admin/loggi
|
|||
|
||||
## 插件开发
|
||||
|
||||
[插件开发示例-sshfs](https://rootsongjc.github.io/docker-practice/docs/plugin_developing)
|
||||
[插件开发示例-sshfs](https://jimmysong.io/docker-practice/docs/plugin_developing)
|
||||
|
||||
[我的docker插件开发文章](https://rootsongjc.github.io/blogs/docker-plugin-develop/)
|
||||
[我的docker插件开发文章](https://jimmysong.io/posts/docker-plugin-develop/)
|
||||
|
||||
[Docker17.03-CE插件开发举例](https://rootsongjc.github.io/blogs/docker-plugin-develop/)
|
||||
[Docker17.03-CE插件开发举例](https://jimmysong.io/posts/docker-plugin-develop/)
|
||||
|
||||
**网络插件**
|
||||
|
||||
- [Contiv](https://rootsongjc.github.io/tags/contiv/) 思科出的Docker网络插件,趟坑全记录,目前还无法上生产,1.0正式版还没出,密切关注中。
|
||||
- [Contiv](https://jimmysong.io/tags/contiv/) 思科出的Docker网络插件,趟坑全记录,目前还无法上生产,1.0正式版还没出,密切关注中。
|
||||
- [Calico](https://github.com/calico) 产品化做的不错,已经有人用在生产上了。
|
||||
|
||||
**存储插件**
|
||||
|
||||
## 业界使用案例
|
||||
|
||||
[京东从OpenStack切换到Kubernetes的经验之谈](https://rootsongjc.github.io/docker-practice/docs/jd_transform_to_kubernetes)
|
||||
[京东从OpenStack切换到Kubernetes的经验之谈](https://jimmysong.io/docker-practice/docs/jd_transform_to_kubernetes)
|
||||
|
||||
[美团点评容器平台介绍](https://rootsongjc.github.io/docker-practice/docs/meituan_docker_platform)
|
||||
[美团点评容器平台介绍](https://jimmysong.io/docker-practice/docs/meituan_docker_platform)
|
||||
|
||||
[阿里超大规模docker化之路](https://rootsongjc.github.io/docker-practice/docs/ali_docker)
|
||||
[阿里超大规模docker化之路](https://jimmysong.io/docker-practice/docs/ali_docker)
|
||||
|
||||
[TalkingData-容器技术在大数据场景下的应用Yarn on Docker](http://rootsongjc.github.io/projects/yarn-on-docker/)
|
||||
|
||||
[乐视云基于Kubernetes的PaaS平台建设](https://rootsongjc.github.io/docker-practice/docs/letv_docker)
|
||||
[乐视云基于Kubernetes的PaaS平台建设](https://jimmysong.io/docker-practice/docs/letv_docker)
|
||||
|
||||
## 资源编排
|
||||
|
||||
建议使用kuberentes,虽然比较复杂,但是专业的工具做专业的事情,将编排这么重要的生产特性绑定到docker上的风险还是很大的,我已经转投到kubernetes怀抱了,那么你呢?
|
||||
|
||||
[我的kubernetes探险之旅](https://rootsongjc.github.io/tags/kubernetes/)
|
||||
[我的kubernetes探险之旅](https://jimmysong.io/tags/kubernetes/)
|
||||
|
||||
## 相关资源
|
||||
|
||||
[容器技术工具与资源](https://rootsongjc.github.io/docker-practice/docs/tech_resource)
|
||||
[容器技术工具与资源](https://jimmysong.io/docker-practice/docs/tech_resource)
|
||||
|
||||
[容器技术2016年总结](https://rootsongjc.github.io/docker-practice/docs/container_2016)
|
||||
[容器技术2016年总结](https://jimmysong.io/docker-practice/docs/container_2016)
|
||||
|
||||
## 关于
|
||||
|
||||
Author: [Jimmy Song](https://rootsongjc.github.io/about)
|
||||
Author: [Jimmy Song](https://jimmysong.io/about)
|
||||
|
||||
rootsongjc@gmail.com
|
||||
|
||||
更多关于**Docker**、**MicroServices**、**Big Data**、**DevOps**、**Deep Learning**的内容请关注[Jimmy Song's Blog](https://rootsongjc.github.io),将不定期更新。
|
||||
更多关于**Docker**、**MicroServices**、**Big Data**、**DevOps**、**Deep Learning**的内容请关注[Jimmy Song's Blog](https://jimmysong.io),将不定期更新。
|
|
@ -1,11 +1,11 @@
|
|||
{
|
||||
"title": "Kubernetes Handbook",
|
||||
"description": "Kubernetes中文指南/实践手册",
|
||||
"description": "Kubernetes中文指南/实践手册|kubernetes handbook|jimmysong.io|宋净超",
|
||||
"language": "zh-hans",
|
||||
"author": "Jimmy Song",
|
||||
"links": {
|
||||
"sidebar": {
|
||||
"Home": "https://jimmysong.io"
|
||||
"sidebar": {
|
||||
"Home": "https://jimmysong.io"
|
||||
}
|
||||
},
|
||||
"plugins": [
|
||||
|
@ -51,4 +51,4 @@
|
|||
"token": "11f7d254cfa4e0ca44b175c66d379ecc"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
|
@ -1,4 +1,4 @@
|
|||
## 前言
|
||||
## ConfigMap
|
||||
|
||||
其实ConfigMap功能在Kubernetes1.2版本的时候就有了,许多应用程序会从配置文件、命令行参数或环境变量中读取配置信息。这些配置信息需要与docker image解耦,你总不能每修改一个配置就重做一个image吧?ConfigMap API给我们提供了向容器中注入配置信息的机制,ConfigMap可以被用来保存单个属性,也可以用来保存整个配置文件或者JSON二进制大对象。
|
||||
|
||||
|
|
|
@ -13,7 +13,7 @@ Kubernetes最终将对labels最终索引和反向索引用来优化查询和watc
|
|||
|
||||
## 动机
|
||||
|
||||
Label能够将组织架构映射到系统架构上(就像是康威定律),这样能够更便于微服务的管理,你可以给object打s上如下类型的label:
|
||||
Label能够将组织架构映射到系统架构上(就像是康威定律),这样能够更便于微服务的管理,你可以给object打上如下类型的label:
|
||||
|
||||
- `"release" : "stable"`, `"release" : "canary"`
|
||||
- `"environment" : "dev"`, `"environment" : "qa"`, `"environment" : "production"`
|
||||
|
|
Loading…
Reference in New Issue