Secret
Kubernetes 提供了secret來處理敏感數(shù)據(jù),比如密碼笨奠、token和秘鑰或辖,相比于直接將敏感數(shù)據(jù)配置在Pod定義或者鏡像中,Secret提供了更加安全的機(jī)制(Base64加密),防止數(shù)據(jù)泄露.Sercret 的創(chuàng)建是獨(dú)立于Pod,以數(shù)據(jù)卷的形式掛載到Pod中,Secret的數(shù)據(jù)將以文件的形式保存,容器通過讀取文件可以獲取需要的數(shù)據(jù).
目前Secret的類型有有以下三種:
1窗骑、Opaque(default): 任意字符串
2、kubernetes.io/service-account-token: 作用于ServiceAccount
3软族、kubernetes.io/dockercfg: 作用于Docker registry,用戶下載docker鏡像認(rèn)證使用
Opaque Secret
Opaque 類型的數(shù)據(jù)是一個(gè)map類型,要求value是base64編碼格式:
# echo -n "admin" | base64
YWRtaW4=
# echo -n "1f2d1e2e67df" | base64
MWYyZDFlMmU2N2Rm
#cat secrets.yml
apiVersion: v1
kind: Secret
metadata:
name: mysecret
type: Opaque
data:
password: MWYyZDFlMmU2N2Rm
username: YWRtaW4=
#kubectl create -f secrets.yml -n default
secret/mysecret created
驗(yàn)證創(chuàng)建的Secrets
12345.png
secret 引用方式
1、Volume方式
2、環(huán)境變量方式
Secret掛載到Volume中
apiVersion: v1
kind: Pod
metadata:
labels:
name: db
name: db
spec:
volumes:
- name: secrets
secret:
secretName: mysecret
containers:
- image: gcr.io/my_project_id/pg:v1
name: db
volumeMounts:
- name: secrets
mountPath: "/apps/conf/secrets"
readOnly: true
ports:
- name: cp
containerPort: 5432
hostPort: 5432
Secret導(dǎo)出到環(huán)境變量中
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: wordpress-deployment
spec:
replicas: 2
strategy:
type: RollingUpdate
template:
metadata:
labels:
app: wordpress
visualize: "true"
spec:
containers:
- name: "wordpress"
image: "wordpress"
ports:
- containerPort: 80
env:
- name: WORDPRESS_DB_USER
valueFrom:
secretKeyRef:
name: mysecret
key: username
- name: WORDPRESS_DB_PASSWORD
valueFrom:
secretKeyRef:
name: mysecret
key: password
kubernetes.io/dockerconfigjson
直接用kubectl命令來創(chuàng)建用于docker registry認(rèn)證的secret:
# kubectl create secret docker-registry myregistrykey --docker-server=DOCKER_REGISTRY_SERVER --docker-username=DOCKER_USER --docker-password=DOCKER_PASSWORD --docker-email=DOCKER_EMAIL
secret "myregistrykey" created.
也可以直接讀取~/.docker/config.json的內(nèi)容來創(chuàng)建
# cat ~/.docker/config.json | base64
# cat > myregistrykey.yaml <<EOF
apiVersion: v1
kind: Secret
metadata:
name: myregistrykey
data:
.dockerconfigjson: UmVhbGx5IHJlYWxseSByZWVlZWVlZWVlZWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWFhYWxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGxsbGx5eXl5eXl5eXl5eXl5eXl5eXl5eSBsbGxsbGxsbGxsbGxsbG9vb29vb29vb29vb29vb29vb29vb29vb29vb25ubm5ubm5ubm5ubm5ubm5ubm5ubm5ubmdnZ2dnZ2dnZ2dnZ2dnZ2dnZ2cgYXV0aCBrZXlzCg==
type: kubernetes.io/dockerconfigjson
EOF
$ kubectl create -f myregistrykey.yaml
在創(chuàng)建Pod的時(shí)候,通過imagePullSecrets來引用剛創(chuàng)建的myregistrykey:
apiVersion: v1
kind: Pod
metadata:
name: foo
spec:
containers:
- name: foo
image: janedoe/awesomeapp:v1
imagePullSecrets:
- name: myregistrykey
Service Account
Service Account用來訪問Kubernetes API,由Kubernetes自動(dòng)創(chuàng)建蹄梢,并且會(huì)自動(dòng)掛載到Pod的/run/secrets/kubernetes.io/serviceaccount目錄中
$ kubectl run nginx --image nginx
deployment "nginx" created
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-3137573019-md1u2 1/1 Running 0 13s
$ kubectl exec nginx-3137573019-md1u2 ls /run/secrets/kubernetes.io/serviceaccount
ca.crt
namespace
token