3 ms·
CockroachDB annoyingly requires manual certificate creation and distribution to each node, and if you don't set those up then you can't use any authorization at
by manigandham 7y ago
CockroachDB annoyingly requires manual certificate creation and distribution to each node, and if you don't set those up then you can't use any authorization at all. It's strange and user-hostile to disable auth completely just because you don't use certs.
Also some environments like Kubernetes might already have network encryption (provided by a service mesh) and don't need another layer.
Certificates serve both encryption and authentication, but encryption can be done with self-signed certs automatically generated by the nodes upon joining the cluster and authentication can be handled in the joining process by using a token or some other bootstrap value that's easier to manage.
- knz42 7y ago> CockroachDB annoyingly requires manual certificate creation and distribution to each node, and if you don't set those up then you can't use any authorization at all. It's strange and user-hostile to disable auth completely just because you don't use certs. This comment is not any more true as of CockroachDB 20.1 (Upcoming in Q2 2020). This version will enable you to set up your own transport-level security with clients using password authentication to crdb.
- deleted 7y ago[deleted]