my-rook-config

Files

T

Blaine Gardner 7bb72a0171 object: also use system certs for validating RGW cert

When generating the HTTP client used for RGW admin ops, use both system
certs as well as the user-given cert.

As a real world example, admins may use ACME to rotate Letsencrypt certs
every 2 months. For an external CephObjectStore, the cert used by Rook
and RGW may not be rotated at the same time. This can cause the Rook
operator to fail CephObjectStore reconciliation until both certs agree.

When Rook also relies on system certs in the container, Rook's
reconciliation will not have reconciliation failures because
Letsencrypt's well-known and trusted root certificates can be loaded
from the system to validate the RGW's newly-rotated cert.

Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>

2024-10-25 11:22:11 -06:00

client

build: update controller runtime to v0.18.4

2024-07-05 09:05:12 +05:30

cluster

test: wait for mon daemons rather than mon canaries

2024-10-25 09:17:02 -06:00

config

core: remove support for ceph quincy

2024-10-03 11:12:55 -06:00

controller

core: define empty securityContext for pods to fix CIS 5.7.3