Configure a cert-manager DNS01 webhook solver for a DNS provider without built-in support

Steps

1. Confirm no in-tree provider fits (ACMEDNS, Akamai, AzureDNS, Cloudflare, DigitalOcean, Google CloudDNS, RFC2136, Route53) and check for an existing community solver on the cert-manager-webhook GitHub topic before writing your own.
2. Scaffold a solver implementing the webhook.Solver interface (Name, Present, CleanUp, Initialize), using the cert-manager/webhook-example repository as the template, and deploy it as its own Deployment/Service registered as a Kubernetes APIService.
3. Run the DNS01 provider conformance test suite included in the webhook-example repo against your implementation before wiring it into any Issuer - this is required by cert-manager's own DNS provider guidelines.
4. In the Issuer or ClusterIssuer, add a solvers[].dns01.webhook block with groupName (a unique API group you control, e.g. acme.mycompany.com), solverName (must exactly match what your Solver.Name() returns), and a config block holding provider-specific settings.
5. Verify groupName and solverName in the Issuer match the values registered by the webhook's APIService/Helm chart exactly, since cert-manager routes ACME Present/CleanUp calls to your webhook purely based on this group name match.