pivotal-cf/pks-kubo-etcd

Name: pks-kubo-etcd

Owner: Pivotal Cloud Foundry

Description: null

Created: 2018-02-21 14:37:51.0

Updated: 2018-04-05 09:39:19.0

Pushed: 2018-05-10 15:52:48.0

Homepage: null

Size: 2755

Language: Go

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Kubo-etcd release

This is a fork of the cloudfoundry-incubator/etcd-release. This is actively used in the KuBo project (https://github.com/cloudfoundry-incubator/kubo-deployment). It uses ETCD v3 underneath.

For the original documentation on how to use etcd release, navigate to the README here

Configuring kubo-etcd with TLS

When configuring the original etcd-release with TLS, consul was a required dependency as communication to the etcd nodes were done by consul DNS addresses.

For Kubo, DNS addresses are managed by BOSH DNS meaning the certificates generated for peer and client/server TLS communication must be generated accordingly. Given the bosh property etcd.advertise_urls_dns_suffix is set (i.e. etcd.kubo), the certificates must have the following configuration:

• Common Name (CN): etcd.kubo
• Subject Alternative Names (SANs): etcd.kubo, *.etcd.kubo