Skip to content

Commit

Permalink
Address comments
Browse files Browse the repository at this point in the history
Signed-off-by: Joe Nathan Abellard <contact@jabellard.com>
  • Loading branch information
jabellard committed Nov 8, 2024
1 parent e219738 commit 0602866
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/proposals/karmada-operator/custom_ca_cert/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,15 +31,15 @@ By enabling users to specify a custom CA certificate, this feature ensures that

### Goals

- Allow users to specify a custom CA certificate which is used to sign the Karmada API Server certificate and for verifying client certificates
- Allow users to specify a custom CA certificate which is used to sign the Karmada API Server certificate and for verifying client certificates.
- Ensure that control plane instances deployed across multiple management clusters that span multiple data centers use the same CA, enabling secure and seamless cross-data center communication.
- Enable operators to align Karmada control plane PKI with organizational policies for high availability and security.

### Non-Goals

- Change the default behavior of the Karmada operator when no custom CA is provided.
- Alter the process of how control planes are connected to etcd.
- Address custom CA requirements for other concerns such as PKI for an in-cluster ETCD instance or front proxy communications
- Address custom CA requirements for other concerns such as PKI for an in-cluster ETCD instance or front proxy communications.

## Proposal

Expand Down

0 comments on commit 0602866

Please sign in to comment.