github/dynamiclistener
1
0
Fork 1
mirror of https://github.com/rancher/dynamiclistener.git synced 2025-06-21 12:37:05 +00:00
Code Issues Projects Releases Wiki Activity
167 Commits 23 Branches 45 Tags 2.5 MiB
Go 100%
main
Go to file
Chad Roberts 6144f3d8db
Update VERSION.md for v0.7 (#181)
2025-06-11 15:06:36 -04:00
.github Check certificate fingerprint when deciding if memory store needs to be updated (#180) 2025-06-11 10:52:11 -07:00
cert always use CATTLE_NEW_SIGNED_CERT_EXPIRATION_DAYS when generating a certificate 2022-07-20 12:07:31 -07:00
factory Check certificate fingerprint when deciding if memory store needs to be updated (#180) 2025-06-11 10:52:11 -07:00
server Revert change using !errors.Is(...) vs err != ... 2024-08-29 13:54:15 -07:00
storage Check certificate fingerprint when deciding if memory store needs to be updated (#180) 2025-06-11 10:52:11 -07:00
filter.go Add filter helper method 2020-11-09 21:52:17 -07:00
go.mod feat: bump dependencies for Kubernetes 1.33 support (#179) 2025-06-11 13:00:39 -04:00
go.sum feat: bump dependencies for Kubernetes 1.33 support (#179) 2025-06-11 13:00:39 -04:00
LICENSE Initial Commit 2019-05-09 12:36:03 -07:00
listener_test.go Tests for Marking additional connections as ready 2022-10-19 12:32:07 -07:00
listener.go Use more Verbose name for Listener 2023-07-14 08:28:47 +02:00
README.md Implement versioning ADR (#124) 2024-11-15 09:36: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
VERSION.md Update VERSION.md for v0.7 (#181) 2025-06-11 15:06:36 -04:00

README.md

dynamiclistener

DynamicListener allows you to setup a server with automatically generated (and re-generated) TLS certs with kubernetes secrets integration.

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

Versioning

See VERSION.md.