search

zachomedia / cert-manager-webhook-pdns

A PowerDNS webhook for cert-manager
MIT License
57 stars 33 forks source link

Just annoying message (loading OpenAPI spec for "v1alpha1...." failed) #23

Open EnochTheWise opened 2 years ago

EnochTheWise commented 2 years ago

Hi ;o)

kubernetes: v1.22.4 cert-manager: v1.9.1 cert-manager-webhook-pdns: v2.2.0

kube-apiserver log messages:

E0810 07:18:21.893411       1 controller.go:116] loading OpenAPI spec for "v1alpha1.fintechiq" failed with: OpenAPI spec does not exist
I0810 07:18:21.893429       1 controller.go:129] OpenAPI AggregationController: action for item v1alpha1.fintechiq: Rate Limited Requeue.
zachomedia commented 2 years ago

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.

EnochTheWise commented 2 years ago

Hi 8)

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?

E0815 02:59:57.617695       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: Failed to watch *v1beta2.FlowSchema: failed to list *v1beta2.FlowSchema: the server could not find the requested resource
W0815 02:59:58.536460       1 reflector.go:324] pkg/mod/k8s.io/client-go@v0.24.1/tools/cache/reflector.go:167: failed to list *v1beta2.PriorityLevelConfiguration: the server could not find the requested resource
ghost commented 2 years ago

Hello @zachomedia , i have same issue as @EnochTheWise. Logs from pod is

W0914 18:02:05.994387       1 reflector.go:324] pkg/mod/k8s.io/client-go@v0.24.1/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/client-go@v0.24.1/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/client-go@v0.24.1/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/client-go@v0.24.1/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 Is it possible to switch v1beta2.flow... to v1beta1.flow...?

googled that this error not affects anything.

zachomedia commented 2 years ago

@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.

ghost commented 2 years ago

k8s version 1.21.14. But i suppose that some libraries ( maybe go lib ) queries all know versions and print those, which can't find. I successfully set this webhook up, so this error not affect anything.

EnochTheWise commented 1 year ago

A some addition. ApiService is exist:


$ k get apiservices v1alpha1.v1alpha1.fintechiq
NAME               SERVICE                                  AVAILABLE   AGE
v1alpha1.fintechiq   cert-manager/cert-manager-webhook-pdns   True        64d