Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type DPFProviderSolverConfig ¶
type DPFProviderSolverConfig struct {
Endpoint string `json:"endpoint"`
TokenSecretRef cmmeta.SecretKeySelector `json:"tokenSecretRef"`
}
type DPFSolver ¶
type DPFSolver struct {
// contains filtered or unexported fields
}
customDNSProviderSolver implements the provider-specific logic needed to 'present' an ACME challenge TXT record for your own DNS provider. To do so, it must implement the `github.com/cert-manager/cert-manager/pkg/acme/webhook.Solver` interface.
func (*DPFSolver) CleanUp ¶
func (c *DPFSolver) 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 (*DPFSolver) Initialize ¶
func (c *DPFSolver) Initialize(kubeClientConfig *restclient.Config, stopCh <-chan struct{}) error
func (*DPFSolver) Name ¶
Name is used as the name for this DNS solver when referencing it on the ACME Issuer resource. This should be unique **within the group name**, i.e. you can have two solvers configured with the same Name() **so long as they do not co-exist within a single webhook deployment**. For example, `cloudflare` may be used as the name of a solver.
func (*DPFSolver) Present ¶
func (c *DPFSolver) 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