Merge pull request #351 from jonboulle/master

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Fix various typos in spelling of Certificate
This commit is contained in:
jetstack-ci-bot 2018-03-12 10:14:09 +00:00 committed by GitHub
commit ce9e5ede2b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 10 additions and 10 deletions

View File

@ -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.

View File

@ -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.

View File

@ -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.

View File

@ -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
}