rancher/dynamiclistener
1
0
Fork 0
forked from github/dynamiclistener
Code Issues Pull Requests Projects Releases Wiki Activity
fork to support Chinese encryption set
101 Commits 4 Branches 17 Tags 210 KiB
Go 100%
9b92d13bcb
Go to file
Brad Davidson 9b92d13bcb Fix initial secret not being written to Kubernetes 
Updates to the secret that occurred before the controller was done
syncing were not being written to Kubernetes. Subsequent updates to the
secret would eventually get it written, but Rancher requires that the
cert be written immediately. This was probably an unnecessary
optimization anyway, so back it out in favor of just checking to see if
the secrets controller is available.

Also fixed improper handling of multiple goroutines attempting to create
the Kubernetes secret at the same time; this was also handled eventually
but caused an unnecessary round of extra writes to the secret.

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
2022-05-20 12:21:30 -07:00
cert Move Kubernetes Secrets storage update to goroutine 2022-05-02 18:48:48 -07:00
factory Move Kubernetes Secrets storage update to goroutine 2022-05-02 18:48:48 -07:00
server Pass context to http server as BaseContext 2021-06-15 22:42:42 -07:00
storage Fix initial secret not being written to Kubernetes 2022-05-20 12:21:30 -07:00
filter.go Add filter helper method 2020-11-09 21:52:17 -07:00
go.mod Move Kubernetes Secrets storage update to goroutine 2022-05-02 18:48:48 -07:00
go.sum Fix listenAndServe certificate expiration by preloading certs 2021-11-23 23:38:49 -08:00
LICENSE Initial Commit 2019-05-09 12:36:03 -07:00
listener.go Move Kubernetes Secrets storage update to goroutine 2022-05-02 18:48:48 -07:00
README.md Add README 2021-11-19 13:50:48 -05:00
redirect.go Fix acme listener 2020-02-07 14:20:45 -07:00
tcp.go Refactor to not include a server by default 2019-10-30 19:14:34 -07:00

README.md

dynamiclistener

This README is a work in progress; aimed towards providing information for navigating the contents of this repository.

Changing the Expiration Days for Newly Signed Certificates

By default, a newly signed certificate is set to expire 365 days (1 year) after its creation time and date. You can use the CATTLE_NEW_SIGNED_CERT_EXPIRATION_DAYS environment variable to change this value.

Please note: the value for the aforementioned variable must be a string representing an unsigned integer corresponding to the number of days until expiration (i.e. X509 "NotAfter" value).