Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Ns1DNSProviderSolver ¶
type Ns1DNSProviderSolver struct {
// contains filtered or unexported fields
}
Ns1DNSProviderSolver implements the logic needed to 'present' an ACME challenge TXT record. To do so, it implements the `github.com/cert-manager/cert-manager/pkg/acme/webhook.Solver` interface.
func (*Ns1DNSProviderSolver) CleanUp ¶
func (c *Ns1DNSProviderSolver) CleanUp(ch *v1alpha1.ChallengeRequest) error
CleanUp should delete the relevant TXT record from the DNS provider console. If multiple TXT records exist with the same record name (e.g. _acme-challenge.example.com) then **only** the record with the same `key` value provided on the ChallengeRequest should be cleaned up. This is in order to facilitate multiple DNS validations for the same domain concurrently.
func (*Ns1DNSProviderSolver) Initialize ¶
func (c *Ns1DNSProviderSolver) Initialize(kubeClientConfig *k8sRest.Config, _ <-chan struct{}) error
Initialize will be called when the webhook first starts. This method can be used to instantiate the webhook, i.e. initialising connections or warming up caches. Typically, the kubeClientConfig parameter is used to build a Kubernetes client that can be used to fetch resources from the Kubernetes API, e.g. Secret resources containing credentials used to authenticate with DNS provider accounts. The stopCh can be used to handle early termination of the webhook, in cases where a SIGTERM or similar signal is sent to the webhook process.
func (*Ns1DNSProviderSolver) Name ¶
func (c *Ns1DNSProviderSolver) Name() string
Name is used as the name for this DNS solver when referencing it on the ACME Issuer resource.
func (*Ns1DNSProviderSolver) Present ¶
func (c *Ns1DNSProviderSolver) Present(ch *v1alpha1.ChallengeRequest) error
Present is responsible for actually presenting the DNS record with the DNS provider. This method should tolerate being called multiple times with the same value. cert-manager itself will later perform a self check to ensure that the solver has correctly configured the DNS provider.
Source Files