-
Notifications
You must be signed in to change notification settings - Fork 442
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
failed with: OpenAPI spec does not exist #27
Comments
I have got the same error with the freenom dsn resolver. Still no idea on how to fix it. |
I have the same issue with Cert Manager Webhook for Dynu Any idea? |
Perhaps the group name in chart values has not been changed https://github.com/cert-manager/webhook-example/blob/master/deploy/example-webhook/values.yaml#L9 ? If it seems like the webhook repository does not reference |
Looking at the referenced cert manager webhooks (dynu, freenom, and others on GitHub) and my own, it looks like the error messages are present even if we update the group name to something explicit. It seems another project implements the openapi spec kubernetes-sigs/prometheus-adapter#335 May need to implement this: https://github.com/kubernetes/kube-openapi |
I got the same problem with PowerDNS webhook, still no fix? |
Update: Ignore this, my issue is different, seems to be a problem with using too new of a version of I hit what appears to be a variation of this on my attempt at a custom webhook for Porkbun
I dug into the webhook code and nothing obvious stuck out to me. |
@bcspragu if you are still interested / haven't solved your problem yet, consider this: I ran into the same error message and as it turns out, the problem was the go version used in the I overcame the problem by looking at other working hooks, realizing the most recent version any of them used was: FROM golang:1.19-alpine AS build_deps If you set your Dockerfile to use v1.19, your problem will likely disappear. To make my build work, I referenced the webhook for google-domains, merging their |
Thanks for the tip! In my case, I don't remember the exact resolution, but I think I had fixed my issue by just not upgrading |
This issue should be now solved.
I haven't seen a single error across my cluster for the last 24 hours. Note that upgrading to cert-manager to 1.13.0 alone isn't enough. The webhook needs to be compiled against cert-manager 1.13.0. Here is an excerpt of my go 1.20
require (
github.com/cert-manager/cert-manager v1.13.0
github.com/ovh/go-ovh v1.4.2
k8s.io/api v0.28.1
k8s.io/apiextensions-apiserver v0.28.1
k8s.io/apimachinery v0.28.1
k8s.io/client-go v0.28.1
) |
Whilst I can confirm building against v1.13 works when also deploying with the same version, the information provided is incomplete. More development has to be done for the hook to actually work:
|
@irreleph4nt I'm not part of the cert-manager/jetstack team but what you describe sounds like separate issues (though connected perhaps). Have you considered raising separate issues and linking them to this one? On your 2nd point, do you have more details and some code to propose? |
I really appreciate you all commenting here and discussing this! We (the maintainer team) are stretched pretty thin at the moment and it looks like the webhook-example has passed us by a bit. I've put out a call to action to hopefully get someone to take a look at this repo soon! Thank you all for being part of the community, appreciate you all! ❤️ |
Likewise @SgtCoDFish we all also very much appreciate all the work you and the entire team are doing. |
Hi, I'm trying to implement Hetzner DNS API based on this sample, Everything is working as expected and the webhook issue the certificates normally, however, I'm getting this log error constantly:
any idea how to fix it?
The text was updated successfully, but these errors were encountered: