Pods contd
Dealing with environmental variables
docker run -d --name mysqldb \
-e MYSQL_ROOT_PASSWORD=qtdevops \
-e MYSQL_DATABASE=nop \
-e MYSQL_USER=qtdevops \
-e MYSQL_PASSWORD=qtdevops \
mysql:latest
- Activity 4: lets try writing a manifest to create a mysql container in a Pod
---
apiVersion: v1
kind: Pod
metadata:
name: forth
spec:
containers:
- name: mysql
image: mysql:latest
env:
- name: MYSQL_ROOT_PASSWORD
value: qtdevops
- name: MYSQL_USER
value: qtdevops
- name: MYSQL_PASSWORD
value: qtdevops
- name: MYSQL_DATABASE
value: nop

Dealing with commands or entrypoints
- Certain containers we might need to pass a CMD
docker run -d --name test alpine sleep 1d
- Lets try writing a manifest for this
---
apiVersion: v1
kind: Pod
metadata:
name: fifth
spec:
containers:
- name: alp
image: alpine
args:
- sleep
- 1d
Resources in kuberntes
- Refer Here for resources and limits
- A pod With resources defined has an impact on QoS
---
apiVersion: v1
kind: Pod
metadata:
name: second
spec:
containers:
- name: first
image: nginx
- name: second
image: alpine
command:
- sleep
- 1d
Like this:
Like Loading...