Skip to content

Commit

Permalink
Add information about expiration to service serving certificate secrets
Browse files Browse the repository at this point in the history
  • Loading branch information
soltysh committed Jan 2, 2017
1 parent 97bb9ba commit 299fc9d
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions dev_guide/secrets.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,8 @@ to use for your secret. Then, your *PodSpec* can mount that secret. When it is
available, your pod will run. The certificate will be good for the internal
service DNS name, `*<service.name>.<service.namespace>.svc*`. The certificate
and key are in PEM format, stored in `*tls.crt*` and `*tls.key*` respectively.
They will be regenerated upon expiry, you can view the expiration date in
`*service.alpha.openshift.io/expiry*` annotation, which is in RFC3339 format.

Other pods can trust cluster-created certificates (which are only signed for
internal DNS names), by using the CA bundle in the
Expand Down

0 comments on commit 299fc9d

Please sign in to comment.