148 lines
3.9 KiB
Markdown
148 lines
3.9 KiB
Markdown
## 1. 在容器中获取 Pod 的IP
|
||
|
||
通过环境变量来实现，该环境变量直接引用 resource 的状态字段，示例如下：
|
||
|
||
```Yaml
|
||
apiVersion: v1
|
||
kind: ReplicationController
|
||
metadata:
|
||
name: world-v2
|
||
spec:
|
||
replicas: 3
|
||
selector:
|
||
app: world-v2
|
||
template:
|
||
metadata:
|
||
labels:
|
||
app: world-v2
|
||
spec:
|
||
containers:
|
||
- name: service
|
||
image: test
|
||
env:
|
||
- name: POD_IP
|
||
valueFrom:
|
||
fieldRef:
|
||
fieldPath: status.podIP
|
||
ports:
|
||
- name: service
|
||
containerPort: 777
|
||
```
|
||
|
||
容器中可以直接使用 `POD_IP` 环境变量获取容器的 IP。
|
||
|
||
## 2. 指定容器的启动参数
|
||
|
||
我们可以在 Pod 中为容器使用 command 为容器指定启动参数：
|
||
|
||
```Bash
|
||
command: ["/bin/bash","-c","bootstrap.sh"]
|
||
```
|
||
|
||
看似很简单，使用数组的方式定义，所有命令使用跟 Dockerfile 中的 CMD 配置是一样的，但是有一点不同的是，`bootsttap.sh` 必须具有可执行权限，否则容器启动时会出错。
|
||
|
||
## 3. 让Pod调用宿主机的docker能力
|
||
|
||
我们可以想象一下这样的场景，让 Pod 来调用宿主机的 docker 能力，只需要将宿主机的 `docker` 命令和 `docker.sock` 文件挂载到 Pod 里面即可，如下：
|
||
|
||
```Yaml
|
||
apiVersion: v1
|
||
kind: Pod
|
||
metadata:
|
||
name: busybox-cloudbomb
|
||
spec:
|
||
containers:
|
||
- image: busybox
|
||
command:
|
||
- /bin/sh
|
||
- "-c"
|
||
- "while true; \
|
||
do \
|
||
docker run -d --name BOOM_$(cat /dev/urandom | tr -cd 'a-f0-9' | head -c 6) nginx ; \
|
||
done"
|
||
name: cloudbomb
|
||
volumeMounts:
|
||
- mountPath: /var/run/docker.sock
|
||
name: docker-socket
|
||
- mountPath: /bin/docker
|
||
name: docker-binary
|
||
volumes:
|
||
- name: docker-socket
|
||
hostPath:
|
||
path: /var/run/docker.sock
|
||
- name: docker-binary
|
||
hostPath:
|
||
path: /bin/docker
|
||
```
|
||
|
||
参考：[Architecture Patterns for Microservices in Kubernetes](https://www.infoq.com/presentations/patterns-microservices-kubernetes)
|
||
|
||
## 4. 使用Init container初始化应用配置
|
||
|
||
Init container可以在应用程序的容器启动前先按顺序执行一批初始化容器，只有所有Init容器都启动成功后，Pod才算启动成功。看下下面这个例子（来源：[kubernetes: mounting volume from within init container - Stack Overflow](https://stackoverflow.com/questions/44109308/kubernetes-mounting-volume-from-within-init-container)）：
|
||
|
||
```yaml
|
||
apiVersion: v1
|
||
kind: Pod
|
||
metadata:
|
||
name: init
|
||
labels:
|
||
app: init
|
||
annotations:
|
||
pod.beta.kubernetes.io/init-containers: '[
|
||
{
|
||
"name": "download",
|
||
"image": "axeclbr/git",
|
||
"command": [
|
||
"git",
|
||
"clone",
|
||
"https://github.com/mdn/beginner-html-site-scripted",
|
||
"/var/lib/data"
|
||
],
|
||
"volumeMounts": [
|
||
{
|
||
"mountPath": "/var/lib/data",
|
||
"name": "git"
|
||
}
|
||
]
|
||
}
|
||
]'
|
||
spec:
|
||
containers:
|
||
- name: run
|
||
image: docker.io/centos/httpd
|
||
ports:
|
||
- containerPort: 80
|
||
volumeMounts:
|
||
- mountPath: /var/www/html
|
||
name: git
|
||
volumes:
|
||
- emptyDir: {}
|
||
name: git
|
||
```
|
||
|
||
这个例子就是用来再应用程序启动前首先从GitHub中拉取代码并存储到共享目录下。
|
||
|
||
关于Init容器的更详细说明请参考 [init容器](../concepts/init-containers.md)。
|
||
|
||
## 5. 使容器内时间与宿主机同步
|
||
|
||
我们下载的很多容器内的时区都是格林尼治时间，与北京时间差8小时，这将导致容器内的日志和文件创建时间与实际时区不符，有两种方式解决这个问题：
|
||
|
||
- 修改镜像中的时区配置文件
|
||
- 将宿主机的时区配置文件`/etc/localtime`使用volume方式挂载到容器中
|
||
|
||
第二种方式比较简单，不需要重做镜像，只要在应用的yaml文件中增加如下配置：
|
||
|
||
```yaml
|
||
volumeMounts:
|
||
- name: host-time
|
||
mountPath: /etc/localtime
|
||
readOnly: true
|
||
volumes:
|
||
- name: host-time
|
||
hostPath:
|
||
path: /etc/localtime
|
||
```
|
||
|