You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2020. It is now read-only.
time="2017-05-03T16:36:23Z" level=warning msg="Task failed" _block=spin _module=scheduler-task consecutive failure limit=10 consecutive failures=8 error="rpc error: code = 2 desc = Get https://172.27.128.1:443/api/v1/pods: x509: cannot validate certificate for 172.27.128.1 because it doesn't contain any IP SANs" task-id=b054cf6a-af81-4a54-ae45-8fd4be755d71 task-name=Task-b054cf6a-af81-4a54-ae45-8fd4be755d71
time="2017-05-03T16:36:33Z" level=error msg="collector run error" _module=scheduler-job block=run error="rpc error: code = 2 desc = Get https://172.27.128.1:443/api/v1/pods: x509: cannot validate certificate for 172.27.128.1 because it doesn't contain any IP SANs" job-type=collector
Is this something you have seen before?
Thank you
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Getting this error in the kubestate-collector:
time="2017-05-03T16:36:23Z" level=warning msg="Task failed" _block=spin _module=scheduler-task consecutive failure limit=10 consecutive failures=8 error="rpc error: code = 2 desc = Get https://172.27.128.1:443/api/v1/pods: x509: cannot validate certificate for 172.27.128.1 because it doesn't contain any IP SANs" task-id=b054cf6a-af81-4a54-ae45-8fd4be755d71 task-name=Task-b054cf6a-af81-4a54-ae45-8fd4be755d71
time="2017-05-03T16:36:33Z" level=error msg="collector run error" _module=scheduler-job block=run error="rpc error: code = 2 desc = Get https://172.27.128.1:443/api/v1/pods: x509: cannot validate certificate for 172.27.128.1 because it doesn't contain any IP SANs" job-type=collector
Is this something you have seen before?
Thank you
The text was updated successfully, but these errors were encountered: