https://github.com/aellwein/cert-manager-webhook-netcup
cert-manager webhook implementation for use with Netcup provider
https://github.com/aellwein/cert-manager-webhook-netcup
cert-manager-webhook netcup
Last synced: about 2 months ago
JSON representation
cert-manager webhook implementation for use with Netcup provider
- Host: GitHub
- URL: https://github.com/aellwein/cert-manager-webhook-netcup
- Owner: aellwein
- License: apache-2.0
- Created: 2022-04-12T17:05:46.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2026-02-01T12:15:46.000Z (4 months ago)
- Last Synced: 2026-02-01T22:27:28.592Z (4 months ago)
- Topics: cert-manager-webhook, netcup
- Language: Go
- Homepage:
- Size: 831 KB
- Stars: 42
- Watchers: 1
- Forks: 7
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://artifacthub.io/packages/helm/cert-manager-webhook-netcup/cert-manager-webhook-netcup)
[](https://goreportcard.com/report/github.com/aellwein/cert-manager-webhook-netcup)
[](https://github.com/aellwein/cert-manager-webhook-netcup/blob/main/LICENSE)
cert-manager-webhook-netcup
===========================
> ‼️ **Important Note:**
>
> beginning with the version `1.0.45`, all releases are available only via OCI registry:
>
> **[oci://ghcr.io/aellwein/cert-manager-webhook-netcup](https://github.com/aellwein/cert-manager-webhook-netcup/pkgs/container/cert-manager-webhook-netcup%2Fcert-manager-webhook-netcup)**
>
>
[cert-manager](https://cert-manager.io) webhook implementation for use
with [Netcup](https://www.netcup.eu) provider for solving [ACME DNS-01
challenges](https://cert-manager.io/docs/configuration/acme/dns01/).
Usage
-----
For the netcup-specific configuration, you will need to create a Kubernetes
secret, containing your customer number, API key and API password first.
You can do it like following, just place the correct values in the command:
```sh
kubectl create secret generic netcup-secret -n cert-manager --from-literal=customer-number= --from-literal=api-key= --from-literal=api-password=
```
After creating the secret, configure the ``Issuer``/``ClusterIssuer`` of
yours to have the following configuration (as assumed, secret is
called "netcup-secret" and located in namespace "cert-manager"):
```yml
apiVersion: cert-manager.io/v1
kind: Issuer # may also be a ClusterIssuer
...
spec:
solvers:
- dns01:
webhook:
groupName: com.netcup.webhook
solverName: netcup
config:
secretRef: netcup-secret
secretNamespace: cert-manager
```
For more details, please refer to https://cert-manager.io/docs/configuration/acme/dns01/#configuring-dns01-challenge-provider
Now, the actual webhook can be installed via Helm chart:
```
helm install webhook-netcup oci://ghcr.io/aellwein/cert-manager-webhook-netcup/cert-manager-webhook-netcup --namespace cert-manager
```
From that point, the issuer configured above should be able to solve
the DNS01 challenges using ``cert-manager-webhook-netcup``.
Disclaimer
----------
I am in no way affiliated or associated with Netcup and this project
is done in my spare time.
License
-------
[Apache 2 License](./LICENSE)