缩放复制设置时kubernetes吊舱自动退出
当我在kubernetes(v1.15.2)仪表板中缩放复制集时,应用程序运行如下:缩放复制设置时kubernetes吊舱自动退出,kubernetes,Kubernetes,当我在kubernetes(v1.15.2)仪表板中缩放复制集时,应用程序运行如下: 起动吊舱 自动退出pod,复制集编号变为0 现在我无法获取日志并找到导致此问题的原因。我应该如何检测错误详细信息?我该怎么解决这个问题?最后,UI没有pod: 这是我的复制集配置: { "kind": "ReplicaSet", "apiVersion": "extensions/v1beta1", "metadata": { "name": "apollo-mysql-565ccb75b
{
"kind": "ReplicaSet",
"apiVersion": "extensions/v1beta1",
"metadata": {
"name": "apollo-mysql-565ccb75bc",
"namespace": "dabai-fat",
"selfLink": "/apis/extensions/v1beta1/namespaces/dabai-fat/replicasets/apollo-mysql-565ccb75bc",
"uid": "d883f690-4d8d-45d4-a556-965d38204900",
"resourceVersion": "28630666",
"generation": 32,
"creationTimestamp": "2020-05-15T12:40:26Z",
"labels": {
"app": "apollo-mysql",
"pod-template-hash": "565ccb75bc"
},
"annotations": {
"deployment.kubernetes.io/desired-replicas": "2",
"deployment.kubernetes.io/max-replicas": "2",
"deployment.kubernetes.io/revision": "1"
},
"ownerReferences": [
{
"apiVersion": "apps/v1",
"kind": "Deployment",
"name": "apollo-mysql",
"uid": "703141cd-d8b9-4554-ac4d-d6fdabb7d0e9",
"controller": true,
"blockOwnerDeletion": true
}
]
},
"spec": {
"replicas": 0,
"selector": {
"matchLabels": {
"app": "apollo-mysql",
"pod-template-hash": "565ccb75bc"
}
},
"template": {
"metadata": {
"creationTimestamp": null,
"labels": {
"app": "apollo-mysql",
"pod-template-hash": "565ccb75bc"
},
"annotations": {
"kubectl.kubernetes.io/restartedAt": "2020-04-18T18:30:58+08:00"
}
},
"spec": {
"volumes": [
{
"name": "mysql-persistent-storage",
"persistentVolumeClaim": {
"claimName": "apollo-mysql-pv-claim"
}
}
],
"containers": [
{
"name": "mysql",
"image": "mysql:5.7",
"ports": [
{
"name": "mysql",
"containerPort": 3306,
"protocol": "TCP"
}
],
"env": [
{
"name": "MYSQL_ROOT_PASSWORD",
"value": "gl4LucnXwLeLwAd29QqJn4"
}
],
"resources": {},
"volumeMounts": [
{
"name": "mysql-persistent-storage",
"mountPath": "/var/lib/mysql"
}
],
"terminationMessagePath": "/dev/termination-log",
"terminationMessagePolicy": "File",
"imagePullPolicy": "IfNotPresent"
}
],
"restartPolicy": "Always",
"terminationGracePeriodSeconds": 30,
"dnsPolicy": "ClusterFirst",
"nodeSelector": {
"app-type": "assistant-app"
},
"securityContext": {},
"schedulerName": "default-scheduler"
}
}
},
"status": {
"replicas": 0,
"observedGeneration": 32
}
}
您可能不想直接与复制集交互。此复制集由部署管理(请参阅输出中的
ownerReferences
),您应该直接使用该部署。例如,从CLI,您可以
kubectl scale deployment apollo-mysql --replicas=2
特别是,如果在部署中更新属性,滚动更新的工作方式是使用新配置创建新的复制集,并更改旧复制集和新复制集的复制副本计数。如果查看复制集,通常会看到其中几个具有类似名称,连接到同一部署,但在稳定状态下,其中只有一个具有非零副本计数
类似于
kubectl卷展栏undo
的命令也取决于现有(零副本)复制集的历史记录。Kubernetes文档中的一些示例对此进行了进一步讨论。您可能不想直接与ReplicaSet交互。此复制集由部署管理(请参阅输出中的ownerReferences
),您应该直接使用该部署。例如,从CLI,您可以
kubectl scale deployment apollo-mysql --replicas=2
特别是,如果在部署中更新属性,滚动更新的工作方式是使用新配置创建新的复制集,并更改旧复制集和新复制集的复制副本计数。如果查看复制集,通常会看到其中几个具有类似名称,连接到同一部署,但在稳定状态下,其中只有一个具有非零副本计数
类似于kubectl卷展栏undo
的命令也取决于现有(零副本)复制集的历史记录。Kubernetes文档一节将通过一些示例对此进行进一步讨论