alibaba / alibaba/SREWorks

minikube完整安装部署失败

Open
#241 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
2k
Forks
430
PR merge metrics
No merged PRs in 30d

Description

软件版本:

> minikube version: v1.33.1
commit: 5883c09216182566a63dff4c326a6fc9ed2982ff
K8S版本
Client Version: v1.30.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0

minikube启动命令:
`minikube start --image-mirror-country=cn --cpus=4 --memory=32gb`

sreworks部署命令:
`helm install sreworks ./ \
--create-namespace --namespace sreworks \
--set global.accessMode="nodePort" \
--set global.images.tag="v1.5" \
--set appmanager.home.url="http://localhost:30767" \
--set global.storageClass="standard" \
--set appmanager.server.jwtSecretKey="123456" \
--set localPathProvisioner=false`

异常的POD:

> sreworks-dataops prod-dataops-kubecost-cost-analyzer-85855bcb65-xf5ld 0/3 Running 0 4h25m
sreworks-dataops prod-dataops-skywalking-skywalking-helm-oap-5c9fcc7d6b-c28b2 0/1 Init:CrashLoopBackOff 30 (40s ago) 3h24m
sreworks sreworks-saas-dataops-init-job-wvxwp 0/1 CrashLoopBackOff 36 (112s ago) 3h24m

其中sreworks-saas-dataops-init-job-wvxwp 有大量异常,片段如下:
` {
"readableGmtCreate": "2024-05-25 08:40:35",
"readableGmtModified": "2024-05-25 08:40:35",
"deployId": 124,
"stageId": "prod",
"readableGmtStart": "2024-05-25 08:40:35",
"readableGmtEnd": "2024-05-25 08:40:35",
"deployProcessId": null,
"id": 2185,
"gmtModified": 1716626435000,
"appId": "dataops",
"clusterId": "master",
"gmtEnd": 1716626435000,
"cost": "0",
"deployErrorMessage": "action=runLocalCommand|command=bash -c \/app\/helm upgrade --install prod-dataops-grafana \/tmp\/appmanager_deploy_component_package14762564411383272485\/saas\/dataops\/api\/grafana\/grafana-chart -f \/tmp\/values3601946629615877091.yaml -n sreworks-dataops --kubeconfig \/tmp\/kubeconfig9449112052867011301.json|retCode=1|output=Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials\n",
"gmtCreate": 1716626435000,
"deployType": "COMPONENT",
"identifier": "HELM|grafana|5.5.7+20230905050156633849",
"namespaceId": "sreworks-dataops",
"gmtStart": 1716626435000,
"deployStatus": "WAIT_FOR_OP",
"deployCreator": "superuser"
},
{
"deployId": 124,
"identifier": "HELM|logstash|4.8.0+20230905050156807132",
"gmtStart": 1716626435000,
"gmtEnd": 1716626435000,
"readableGmtEnd": "2024-05-25 08:40:35",
"deployProcessId": null,
"readableGmtModified": "2024-05-25 08:40:35",
"clusterId": "master",
"namespaceId": "sreworks-dataops",
"cost": "0",
"id": 2184,
"gmtCreate": 1716626435000,
"readableGmtCreate": "2024-05-25 08:40:35",
"deployType": "COMPONENT",
"stageId": "prod",
"deployErrorMessage": "action=runLocalCommand|command=bash -c \/app\/helm upgrade --install prod-dataops-logstash \/tmp\/appmanager_deploy_component_package16371569021117624810\/saas\/dataops\/api\/logstash\/logstash-chart -f \/tmp\/values11925336525625295082.yaml -n sreworks-dataops --kubeconfig \/tmp\/kubeconfig4631260338488066602.json|retCode=1|output=Error: Kubernetes cluster unreachable: the server has asked for the client to provide credentials\n",
"gmtModified": 1716626435000,
"appId": "dataops",
"readableGmtStart": "2024-05-25 08:40:35",
"deployStatus": "WAIT_FOR_OP",
"deployCreator": "superuser"
},
`

这个init-job运行失败,导致dataops依赖的容器创建异常。
“ Kubernetes cluster unreachable: the server has asked for the client to provide credentials ”应该如何解决?

Contributor guide

Open the contributing guide

Research direction

Start with the minikube start and helm install commands in the issue, then inspect the sreworks-saas-dataops-init-job logs and the generated kubeconfig used by Helm. Trace why the Grafana and Logstash upgrades receive “the server has asked for the client to provide credentials.” Done means the init job completes and the dependent dataops pods become healthy.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.