Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 2 additions & 0 deletions docs/.custom_wordlist.txt
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ Downloader
dvipng
enablement
Enablement
eTags
filepath
firewalled
fonts
Expand Down Expand Up @@ -99,6 +100,7 @@ rediraffe
redownloading
rerediraffe
reStructuredText
resync
retrigger(ing)?
Rockcraft
rollout
Expand Down
1 change: 1 addition & 0 deletions docs/redirects.txt
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,7 @@
"livepatch/reference/patch-lifecycle.md" "client/explanation/patches/patch-lifecycle.md"
"livepatch/reference/patch-security.md" "client/reference/patches/patch-security.md"
"livepatch/reference/supported-kernels.md" "client/reference/platform/supported-kernels.md"
"livepatch/reference/kernels.md" "client/reference/platform/supported-kernels.md"
"livepatch_on_prem/explanation/access-control.md" "server/explanation/architecture/access-control.md"
"livepatch_on_prem/explanation/data-sent.md" "server/reference/telemetry/data-sent.md"
"livepatch_on_prem/explanation/index.md" "server/explanation/index.md"
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ In [federated deployments](/server/how-to-guides/patch-management/chain-livepatc

TLS for PostgreSQL connections is supported through the connection string. Include `sslmode=verify-full` (or at minimum `sslmode=require`) in the database connection string to encrypt traffic between the server and PostgreSQL.

For charm deployments, database credentials are obtained through Juju relations (`database` interface with the [PostgreSQL K8s Charm](https://charmhub.io/postgresql-k8s)). TLS for the database connection is managed by the PostgreSQL charm's [TLS integration](https://canonical-charmed-postgresql-k8s.readthedocs-hosted.com/14/tutorial/index.html#enable-encryption-with-tls). The Livepatch charm does not expose separate database credential configuration -- all credentials are exchanged through the Juju relation protocol.
For charm deployments, database credentials are obtained through Juju relations (`database` interface with the [PostgreSQL K8s Charm](https://charmhub.io/postgresql-k8s)). TLS for the database connection is managed by the PostgreSQL charm's [TLS integration](https://canonical.com/data/postgresql/docs/16/how-to/network-and-encryption/enable-tls/). The Livepatch charm does not expose separate database credential configuration -- all credentials are exchanged through the Juju relation protocol.

## Encrypt patch storage connections

Expand Down
Loading