Fix various typos in spelling of Certificate
This commit is contained in:
parent
c4cdd405a4
commit
526d31bbc0
@ -95,7 +95,7 @@ Events:
|
||||
Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain example.com
|
||||
Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain www.example.com
|
||||
Normal IssueCertificate 6s cert-manager-controller Issuing certificate...
|
||||
Normal CeritifcateIssued 5s cert-manager-controller Certificated issued successfully
|
||||
Normal CertificateIssued 5s cert-manager-controller Certificate issued successfully
|
||||
```
|
||||
|
||||
You can also check whether issuance was successful with `kubectl get secret example-com-tls -o yaml`. You should see a base64 encoded signed TLS key pair.
|
||||
|
||||
@ -87,7 +87,7 @@ Events:
|
||||
Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain example.com
|
||||
Normal ObtainAuthorization 6s cert-manager-controller Obtained authorization for domain www.example.com
|
||||
Normal IssueCertificate 6s cert-manager-controller Issuing certificate...
|
||||
Normal CeritifcateIssued 5s cert-manager-controller Certificated issued successfully
|
||||
Normal CertificateIssued 5s cert-manager-controller Certificate issued successfully
|
||||
```
|
||||
|
||||
You can also check whether issuance was successful with `kubectl get secret example-com-tls -o yaml`. You should see a base64 encoded signed TLS key pair.
|
||||
|
||||
@ -62,7 +62,7 @@ Events:
|
||||
Warning ErrorCheckCertificate 26s cert-manager-controller Error checking existing TLS certificate: secret "example-com-tls" not found
|
||||
Normal PrepareCertificate 26s cert-manager-controller Preparing certificate with issuer
|
||||
Normal IssueCertificate 26s cert-manager-controller Issuing certificate...
|
||||
Normal CeritifcateIssued 25s cert-manager-controller Certificated issued successfully
|
||||
Normal CertificateIssued 25s cert-manager-controller Certificate issued successfully
|
||||
```
|
||||
|
||||
You can also check whether issuance was successful with `kubectl get secret example-com-tls -o yaml`. You should see a base64 encoded signed TLS key pair.
|
||||
|
||||
@ -38,9 +38,9 @@ const (
|
||||
reasonIssuingCertificate = "IssueCertificate"
|
||||
reasonRenewingCertificate = "RenewCertificate"
|
||||
|
||||
successCeritificateIssued = "CeritifcateIssued"
|
||||
successCeritificateRenewed = "CeritifcateRenewed"
|
||||
successRenewalScheduled = "RenewalScheduled"
|
||||
successCertificateIssued = "CertificateIssued"
|
||||
successCertificateRenewed = "CertificateRenewed"
|
||||
successRenewalScheduled = "RenewalScheduled"
|
||||
|
||||
messageIssuerNotFound = "Issuer %s does not exist"
|
||||
messageIssuerNotReady = "Issuer %s not ready"
|
||||
@ -56,8 +56,8 @@ const (
|
||||
messageIssuingCertificate = "Issuing certificate..."
|
||||
messageRenewingCertificate = "Renewing certificate..."
|
||||
|
||||
messageCertificateIssued = "Certificated issued successfully"
|
||||
messageCertificateRenewed = "Certificated renewed successfully"
|
||||
messageCertificateIssued = "Certificate issued successfully"
|
||||
messageCertificateRenewed = "Certificate renewed successfully"
|
||||
messageRenewalScheduled = "Certificate scheduled for renewal in %d hours"
|
||||
)
|
||||
|
||||
@ -267,7 +267,7 @@ func (c *Controller) issue(ctx context.Context, issuer issuer.Interface, crt *v1
|
||||
|
||||
s = messageCertificateIssued
|
||||
glog.Info(s)
|
||||
c.recorder.Event(crt, api.EventTypeNormal, successCeritificateIssued, s)
|
||||
c.recorder.Event(crt, api.EventTypeNormal, successCertificateIssued, s)
|
||||
|
||||
return nil
|
||||
}
|
||||
@ -311,7 +311,7 @@ func (c *Controller) renew(ctx context.Context, issuer issuer.Interface, crt *v1
|
||||
|
||||
s = messageCertificateRenewed
|
||||
glog.Info(s)
|
||||
c.recorder.Event(crt, api.EventTypeNormal, successCeritificateRenewed, s)
|
||||
c.recorder.Event(crt, api.EventTypeNormal, successCertificateRenewed, s)
|
||||
|
||||
return nil
|
||||
}
|
||||
|
||||
Loading…
Reference in New Issue
Block a user