-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Just annoying message (loading OpenAPI spec for "v1alpha1...." failed) #23
Comments
Hello @EnochTheWise, can you elaborate on what the issue is with the cert-manager-webhook-pdns? Can you provide logs from the cert-manager-webhook-pdns pod? As an aside, I would say your issue in the kube-apiserver logs is with the fintechiq custom resource and not anything related to this project. |
Hi 8)
|
Hello @zachomedia , i have same issue as @EnochTheWise. W0914 18:02:05.994387 1 reflector.go:324] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: failed to list *v1beta2.FlowSchema: the server could not find the requested resource
E0914 18:02:05.994439 1 reflector.go:138] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: Failed to watch *v1beta2.FlowSchema: failed to list *v1beta2.FlowSchema: the server could not find the requested resource
W0914 18:02:21.547800 1 reflector.go:324] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: failed to list *v1beta2.PriorityLevelConfiguration: the server could not find the requested resource
E0914 18:02:21.547838 1 reflector.go:138] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:167: Failed to watch *v1beta2.PriorityLevelConfiguration: failed to list *v1beta2.PriorityLevelConfiguration: the server could not find the requested resource meanwhile cluster not have this api-resources: root@mycluster-master-01 ~ # kubectl api-resources --verbs=list | grep -i flow
flowschemas flowcontrol.apiserver.k8s.io/v1beta1 false FlowSchema
prioritylevelconfigurations flowcontrol.apiserver.k8s.io/v1beta1 false PriorityLevelConfiguration so i think ACME resolver try to work with not existed resources googled that this error not affects anything. |
@EnochTheWise / @ABess-Flant Can you share what version of Kubernetes you're running? I will see if I can reproduce the issue. There is nothing in my code that is loading those resources, so it might be something with the Kubernetes libraries. |
k8s version 1.21.14. |
A some addition.
|
We have same issue :
This is not breaking any functionality but annoying to see those logs. Also I don't know what is real impact on kube-apiserver. |
Hi ;o)
kubernetes: v1.22.4
cert-manager: v1.9.1
cert-manager-webhook-pdns: v2.2.0
kube-apiserver log messages:
The text was updated successfully, but these errors were encountered: