lbcli update logs tls-bundles

AI Tools

Updates an existing TLS bundle.

Note

Log streaming is currently in tech preview.

Synopsis

Replaces the certificates in an existing TLS bundle. The bundle is fully replaced; supply all PEM files you want to keep (the same flags as "create"). Any targets referencing this bundle will automatically use the updated certificates on the next reload.

lbcli update logs tls-bundles

Examples

# Rotate the CA cert for an existing bundle lbcli -J $JWT update logs tls-bundles \ --name=loki-ca-bundle \ --ca-pem=/etc/ssl/certs/loki-ca-new.pem # Update to add client cert + key (upgrade from one-way to mutual TLS) lbcli -J $JWT update logs tls-bundles \ --name=loki-ca-bundle \ --ca-pem=/etc/ssl/certs/loki-ca.pem \ --cert-pem=/etc/ssl/certs/loki-client.pem \ --key-pem=/etc/ssl/private/loki-client-key.pem

Flag	Short	Type	Description
--help	-h	bool	Help for `tls-bundles`.
--name		string	Name of the TLS bundle (required).
--ca-pem		string	Path to the PEM file containing the CA certificate (required).
--cert-pem		string	Path to the PEM file containing the client certificate (optional, required for mTLS).
--key-pem		string	Path to the PEM file containing the client private key (optional, required for mTLS).

Last updated on

Was this page helpful?