On-premise k8s gitlab runner x509: certificate has expired or is not yet valid

Hi,

I got a strange behaver with my GitLab runner which connected to my on-premise Kubernetes.
until last night all of my pipelines worked without any error.

last night we started getting errors such as:

ERROR: Job failed (system failure): error sending request: Post https://kubernetes.default.svc.cluster.local/api/v1/namespaces/gitlab-runner-upgrade/pods/runner-l4qm1j-project-104-concurrent-0j9f6w/exec?command=gitlab-runner-build&container=helper&container=helper&stderr=true&stdin=true&stdout=true: x509: certificate has expired or is not yet valid

I’ve checked all the certificates in my cluster and everything is ok.
kubernetes version:

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:32:14Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

k8s certificate expiration:

root@k8s-master:~# kubeadm alpha  certs  check-expiration
CERTIFICATE                EXPIRES                  RESIDUAL TIME   EXTERNALLY MANAGED
admin.conf                 Aug 18, 2022 09:33 UTC   364d            no
apiserver                  Aug 18, 2022 09:39 UTC   364d            no
apiserver-etcd-client      Aug 12, 2023 16:45 UTC   1y              no
apiserver-kubelet-client   Aug 18, 2022 09:44 UTC   364d            no
controller-manager.conf    Nov 15, 2021 14:16 UTC   88d             no
etcd-healthcheck-client    Aug 12, 2023 16:45 UTC   1y              no
etcd-peer                  Aug 12, 2023 16:45 UTC   1y              no
etcd-server                Aug 12, 2023 16:45 UTC   1y              no
front-proxy-client         Nov 15, 2021 14:16 UTC   88d             no
scheduler.conf             Nov 15, 2021 14:16 UTC   88d             no

any idea why such failure can accord?
also, if more information is needed please just say.

Thanks

1 Like

I am seeing a similar error attempting to register a runner in a Kubernetes cluster managed by Digital Ocean. I would also appreciate information regarding this issue!