Skip to content

Document higher temporary secret lifetime of Trino coordinators #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 22, 2025
Merged

Document higher temporary secret lifetime of Trino coordinators #701

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion modules/concepts/pages/operations/temporary_credentials_lifetime.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,17 @@
Currently the only temporary credentials are TLS certificates.

Many products use TLS to secure the communications, often times customers use the xref:secret-operator:secretclass.adoc#backend-autotls[secret-operator autoTls] backend to create TLS certificates for the Pods on the fly.
To increase security, these temporary credentials have a short lifetime by default, which will result in e.g. Trino coordinator Pods restarting every ~24 hours (minus some safety buffer) to avoid using expired certificates.
To increase security, most of the products temporary credentials have a short lifetime by default, which will result in e.g. Kafka brokers restarting every ~24 hours (minus some safety buffer) to avoid using expired certificates.

All products will have a default temporary secret lifetime of `24h` with the exception of the following Pods:

[cols="2,1"]
|===
|Pods | Default lifetime

|Trino coordinators
| 15d
|===

== Configure the lifetime

Expand Down
Loading