Javascript 在kubernetes上部署时CreateContainerConfiger错误
这是我的部署文件:Javascript 在kubernetes上部署时CreateContainerConfiger错误,javascript,amazon-web-services,kubernetes,kubectl,amazon-eks,Javascript,Amazon Web Services,Kubernetes,Kubectl,Amazon Eks,这是我的部署文件: apiVersion: apps/v1 kind: Deployment metadata: labels: service: udagram-user name: udagram-user spec: replicas: 1 selector: matchLabels: service: udagram-user template: metadata: labels: service: ud
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
service: udagram-user
name: udagram-user
spec:
replicas: 1
selector:
matchLabels:
service: udagram-user
template:
metadata:
labels:
service: udagram-user
spec:
containers:
- image: pranjal121997/udagram-user
name: udagram-user
imagePullPolicy: Always
resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "1024Mi"
cpu: "500m"
env:
- name: POSTGRESS_PASSWORD
valueFrom:
configMapKeyRef:
name: env-config
key: POSTGRESS_PASSWORD
- name: POSTGRESS_USERNAME
valueFrom:
configMapKeyRef:
name: env-config
key: POSTGRESS_USERNAME
- name: URL
valueFrom:
configMapKeyRef:
name: env-config
key: URL
- name: JWT_SECRET
valueFrom:
configMapKeyRef:
name: env-config
key: JWT_SECRET
- name: POSTGRESS_DATABASE
valueFrom:
configMapKeyRef:
name: env-config
key: POSTGRESS_DATABASE
- name: POSTGRESS_HOST
valueFrom:
configMapKeyRef:
name: env-config
key: POSTGRESS_HOST
restartPolicy: Always
通过kubectl create部署时,它会运行到CreateContainerConfigError。以下是kubectl描述pod的输出:
Name: udagram-user-f57f44889-5jtxf
Namespace: default
Priority: 0
Node: ip-172-31-43-242.ap-south-1.compute.internal/172.31.43.242
Start Time: Wed, 20 May 2020 17:58:34 +0530
Labels: pod-template-hash=f57f44889
service=udagram-user
Annotations: kubernetes.io/psp: eks.privileged
Status: Pending
IP: 172.31.33.34
Controlled By: ReplicaSet/udagram-user-f57f44889
Containers:
udagram-user:
Container ID:
Image: pranjal121997/udagram-user
Image ID:
Port: <none>
Host Port: <none>
State: Waiting
Reason: CreateContainerConfigError
Ready: False
Restart Count: 0
Limits:
cpu: 500m
memory: 1Gi
Requests:
cpu: 250m
memory: 64Mi
Environment:
POSTGRESS_PASSWORD: <set to the key 'POSTGRESS_PASSWORD' of config map 'env-config'> Optional: false
POSTGRESS_USERNAME: <set to the key 'POSTGRESS_USERNAME' of config map 'env-config'> Optional: false
URL: <set to the key 'URL' of config map 'env-config'> Optional: false
JWT_SECRET: <set to the key 'JWT_SECRET' of config map 'env-config'> Optional: false
POSTGRESS_DATABASE: <set to the key 'POSTGRESS_DATABASE' of config map 'env-config'> Optional: false
POSTGRESS_HOST: <set to the key 'POSTGRESS_HOST' of config map 'env-config'> Optional: false
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-skqmw (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-skqmw:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-skqmw
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m9s default-scheduler Successfully assigned default/udagram-user-f57f44889-5jtxf to ip-172-31-43-242.ap-south-1.compute.internal
Warning FailedCreatePodSandBox 3m8s kubelet, ip-172-31-43-242.ap-south-1.compute.internal Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "93df5832a932be9ad03d0cfd1bbaaae2c44fed0073f1325e02697fd9f6b391e9" network for pod "udagram-user-f57f44889-5jtxf": NetworkPlugin cni failed to set up pod "udagram-user-f57f44889-5jtxf_default" network: add cmd: failed to assign an IP address to container
Warning FailedCreatePodSandBox 3m7s kubelet, ip-172-31-43-242.ap-south-1.compute.internal Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "ebcf88c3b4d88a19994f6fdd5eee011f257d9e40348f559758e94e7c368da3b2" network for pod "udagram-user-f57f44889-5jtxf": NetworkPlugin cni failed to set up pod "udagram-user-f57f44889-5jtxf_default" network: add cmd: failed to assign an IP address to container
Warning FailedCreatePodSandBox 3m6s kubelet, ip-172-31-43-242.ap-south-1.compute.internal Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "486dd729e6f9781f7440305cadd0ec6a8eb82129b07efaed2dc1b707c5d03f64" network for pod "udagram-user-f57f44889-5jtxf": NetworkPlugin cni failed to set up pod "udagram-user-f57f44889-5jtxf_default" network: add cmd: failed to assign an IP address to container
Warning FailedCreatePodSandBox 3m5s kubelet, ip-172-31-43-242.ap-south-1.compute.internal Failed create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "35e39b69cd153b1a9b76b2fc672dec151afb5aebbce5999712891ab6c2329e9f" network for pod "udagram-user-f57f44889-5jtxf": NetworkPlugin cni failed to set up pod "udagram-user-f57f44889-5jtxf_default" network: add cmd: failed to assign an IP address to container
Normal SandboxChanged 3m4s (x4 over 3m7s) kubelet, ip-172-31-43-242.ap-south-1.compute.internal Pod sandbox changed, it will be killed and re-created.
Warning Failed 2m9s (x5 over 3m2s) kubelet, ip-172-31-43-242.ap-south-1.compute.internal Error: Couldn't find key POSTGRESS_DATABASE in ConfigMap default/env-config
Normal Pulling 114s (x6 over 3m4s) kubelet, ip-172-31-43-242.ap-south-1.compute.internal Pulling image "pranjal121997/udagram-user"
Normal Pulled 112s (x6 over 3m2s) kubelet, ip-172-31-43-242.ap-south-1.compute.internal Successfully pulled image "pranjal121997/udagram-user"
名称:udagram-user-f57f44889-5jtxf
名称空间:默认值
优先级:0
节点:ip-172-31-43-242.ap-south-1.compute.internal/172.31.43.242
开始时间:2020年5月20日星期三17:58:34+0530
标签:pod模板哈希=f57f44889
服务=udagram用户
注释:kubernetes.io/psp:eks.privileged
状态:待定
IP:172.31.33.34
控制人:ReplicaSet/udagram-user-f57f44889
容器:
udagram用户:
容器ID:
图片:pranjal121997/udagram用户
图像ID:
端口:
主机端口:
国家:等待
原因:CreateContainerConfiger错误
就绪:错误
重新启动计数:0
限制:
cpu:500米
内存:1Gi
请求:
中央处理器:250米
内存:64Mi
环境:
POSTGRESS_密码:可选:false
POSTGRESS_用户名:可选:false
URL:可选:false
JWT_机密:可选:false
POSTGRESS_数据库:可选:false
POSTGRESS_主机:可选:false
挂载:
/来自默认令牌skqmw(ro)的var/run/secrets/kubernetes.io/serviceCount
条件:
类型状态
初始化为True
准备错误
集装箱准备好了吗
播客预定为真
卷数:
默认令牌skqmw:
类型:Secret(由Secret填充的卷)
SecretName:默认令牌skqmw
可选:false
QoS等级:Burstable
节点选择器:
容差:node.kubernetes.io/未就绪:不执行300秒
node.kubernetes.io/不可访问:不执行300秒
活动:
从消息中键入原因年龄
---- ------ ---- ---- -------
正常计划的3m9s默认计划程序已成功将default/udagram-user-f57f44889-5jtxf分配给ip-172-31-43-242.ap-south-1.compute.internal
警告失败CreatePodSandbox 3m8s kubelet,ip-172-31-43-242.ap-south-1.compute。内部失败创建pod沙盒:rpc错误:代码=未知描述=无法设置沙盒容器“93DF5832A932BE9AD03D00CFD1BBAAE2C44FED0073F1325E02697FD9F6B391E9”pod“udagram-user-f57f44889-5jtxf”的网络:NetworkPlugin cni未能设置pod“udagram-user-f57f44889-5jtxf_default”网络:add cmd:未能为容器分配IP地址
警告失败CreatePodSandbox 3m7s kubelet,ip-172-31-43-242.ap-south-1.compute。内部失败创建pod sandbox:rpc错误:代码=未知描述=未能设置沙盒容器“EBCF88C3B4D88A19994F6FDD5EEE011F257D9E40348F55975E94E7C368DA3B2”pod网络“udagram-user-F57F54889-5jtxf”:NetworkPlugin cni未能设置pod“udagram-user-f57f44889-5jtxf_default”网络:add cmd:未能为容器分配IP地址
警告失败创建pod沙盒3m6s kubelet,ip-172-31-43-242.ap-south-1.compute。内部失败创建pod沙盒:rpc错误:代码=未知描述=无法设置沙盒容器“486DD729E6F9781F744005CADD0EC6A8EB82129B07EFAED2DC1B707C5D03F64”pod“udagram-user-f57f44889-5jtxf”的网络:NetworkPlugin cni未能设置pod“udagram-user-f57f44889-5jtxf_default”网络:add cmd:未能为容器分配IP地址
警告失败CreatePodSandbox 3m5s kubelet,ip-172-31-43-242.ap-south-1.compute。内部失败创建pod sandbox:rpc错误:代码=未知描述=无法设置沙盒容器“35e39b69cd153b1a9b76b2fc672dec151afb5aebbce5999712891ab6c2329e9f”pod“udagram-user-f57f44889-5jtxf”的网络:NetworkPlugin cni未能设置pod“udagram-user-f57f44889-5jtxf_default”网络:add cmd:未能为容器分配IP地址
正常沙箱更改3m4s(x4/3m7s)kubelet,ip-172-31-43-242.ap-south-1.compute.内部吊舱沙箱更改,将杀死并重新创建。
警告失败2m9s(x5超过3m2s)kubelet,ip-172-31-43-242.ap-south-1.compute。内部错误:在ConfigMap default/env config中找不到密钥POSTGRESS_数据库
正常拉动114s(x6/3m4s)kubelet,ip-172-31-43-242.ap-south-1.compute.内部拉动图像“pranjal121997/udagram用户”
正常拉取112s(x6/3m2)kubelet,ip-172-31-43-242.ap-south-1.compute.internal成功拉取图像“pranjal121997/udagram用户”
我还有另外两个文件:aws-secret.yaml和env-secret.yaml,其中包含我的postgress用户名、密码和访问id,但不知怎的,kubernetes希望所有密钥都出现在env-configmap.yaml中。如何强制群集从机密文件中获取机密?在部署中,yaml
env config
在所有位置都称为configMapKeyRef
。因此,kubernetes希望POSTGRESS_数据库出现在env config
configMap中。您可以使用secretKeyRef
引用包含密钥POSTGRESS\u数据库
的密钥
这里有一个例子
apiVersion: v1
kind: Pod
metadata:
name: env-single-secret
spec:
containers:
- name: envars-test-container
image: nginx
env:
- name: POSTGRESS_DATABASE
valueFrom:
secretKeyRef:
name: postgres-database-secret-name
key: POSTGRESS_DATABASE
在部署中,yamlenv config
在所有位置都称为configMapKeyRef
。因此,kubernetes希望POSTGRESS_数据库出现在env config
configMap中。您可以使用secretKeyRef
引用包含密钥POSTGRESS\u数据库
的密钥
这里有一个例子
apiVersion: v1
kind: Pod
metadata:
name: env-single-secret
spec:
containers:
- name: envars-test-container
image: nginx
env:
- name: POSTGRESS_DATABASE
valueFrom:
secretKeyRef:
name: postgres-database-secret-name
key: POSTGRESS_DATABASE