Expand description
Pure X.509 CA + leaf-cert generation for the operator’s clients-CA bootstrap. Inter-broker mTLS and cert hot-reload tests can reuse it.
No async, no I/O. These helpers return PEM-encoded material that callers persist to Kubernetes Secrets, files, or anywhere else.
Structs§
- Broker
Cert - A broker leaf cert, which is a server cert and a client cert in one.
- CaMaterial
- Self-signed clients-CA material.
- User
Cert - A leaf cert issued by a clients-CA.
not_afteris RFC3339.
Enums§
- CaError
- Subject
AltName - SAN entry for a leaf cert. ECDSA leaf certs accept any mix of DNS names and IP addresses, and the broker-cert path uses a mix.
Functions§
- generate_
clients_ ca - Generate a self-signed clients CA with
Subject = CN=<cn>, O=krabka,BasicConstraints: CA:TRUE, andKeyUsage = keyCertSign|cRLSign. ECDSA P-256. - generate_
cluster_ ca - Generate a self-signed cluster CA.
- issue_
broker_ cert - Sign a broker leaf cert: a server cert and a client cert in one.
- issue_
user_ cert - Sign a leaf client cert with
Subject = CN=<cn>. - renew_
clients_ ca - Re-sign a clients CA cert with an existing key, a same-key renewal.
- renew_
cluster_ ca - Re-sign a cluster CA cert with an existing key, a same-key renewal.