kube apiserver timeout 清理机密资源名称可能不为空时出错 [英] kube apiserver timeout Error cleaning up secrets resource name may not be empty

问题描述

当我在 gitlab 上触发发布时，它失败了，我检查了 gitlab-runner pod 的日志，它显示以下错误:

When I trigger publish on gitlab, it fails and I check the logs of gitlab-runner pod, It shows the error below:

kubectl logs -n gitlab-tur prod-gitlab-ci-runner-0
ERROR: Job failed (system failure): Post https://10.96.0.1:443/api/v1/namespaces/gitlab-tur/secrets: dial tcp 10.96.0.1:443: i/o timeout  duration=1m0.007641837s job=3044 project=25 runner=DwvfWx49
ERROR: Error cleaning up secrets: resource name may not be empty  job=3044 project=25 runner=DwvfWx49

这是截图

版本信息:

root@ubuntu:~# kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T21:03:42Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T20:55:23Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

我好几天都无法向环境发布任何内容.有没有人遇到过这样的问题?

I am not able to publish anything to environments for days. Has anyone experienced such a problem before?

推荐答案

看起来有一种解决方法，方法是删除 k8s 中的 gitlab-runner pod 并按照 这篇文章.

Looks like there is a workaround for that by deleting the gitlab-runner pod in k8s and retrying the process as per this post.

这篇关于kube apiserver timeout 清理机密资源名称可能不为空时出错的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！