etcd job from cfcr-etcd/1.11.1
Github source:
d398cd0 or
master branch
Properties¶
etcd¶
dns_suffix¶If provided, used as a DNS suffix for all nodes in the etcd cluster
metrics_port¶IF provided with etcd.metrics_protocol, metrics endpoints listen on the port. 2379 and 2380 can not be used.
metrics_protocol¶IF provided with etcd.metrics_port, metrics endpoints listen with the protocol. http or https.
tls¶
etcd¶
ca¶CA for etcd client and server authentication
certificate¶Certificate for etcd client and server authentication
private_key¶Private key for etcd client and server authentication
etcdctl¶
ca¶CA for etcdctl client authentication
certificate¶Certificate for etcdctl client authentication
private_key¶Private key for etcdctl client authentication
etcdctl-root¶
certificate¶Certificate for etcdctl client authentication with CN root
private_key¶Private key for etcdctl client authentication with CN root
peer¶
ca¶CA for peer authentication
certificate¶Certificate for peer authentication
private_key¶Private key for peer authentication
users¶
List of user’s name, permissions, path, and whether the path is a prefix. Etcd will use these info to set up rbac rules for these users
- Example
-
|+ - name: root password: ((etcd_user_root_password)) versions: [ "v2", "v3" ] - name: flanneld permissions: read: - /coreos.com/network/* write: - /coreos.com/network/* password: ((etcd_user_flanneld_password)) versions: [ "v2" ] - name: foo permissions: read: - /bar password: pass versions: [ "v2", "v3" ]
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/etcd/ directory
(learn more).
bin/authentication-setup(frombin/authentication-setup.erb)bin/drain(frombin/drain.erb)bin/ensure-member-healthy(frombin/ensure-member-healthy.erb)bin/etcd(frombin/etcd.erb)bin/etcdctl(frombin/etcdctl.erb)bin/post-start(frombin/post-start.erb)bin/pre-start(frombin/pre-start.erb)bin/setup(frombin/setup.erb)bin/utils.sh(frombin/utils.sh.erb)config/bpm.yml(fromconfig/bpm.yml.erb)config/etcd-ca.crt(fromconfig/etcd-ca.crt.erb)config/etcd.crt(fromconfig/etcd.crt.erb)config/etcd.key(fromconfig/etcd.key.erb)config/etcdctl-ca.crt(fromconfig/etcdctl-ca.crt.erb)config/etcdctl-root.crt(fromconfig/etcdctl-root.crt.erb)config/etcdctl-root.key(fromconfig/etcdctl-root.key.erb)config/etcdctl.crt(fromconfig/etcdctl.crt.erb)config/etcdctl.key(fromconfig/etcdctl.key.erb)config/peer-ca.crt(fromconfig/peer-ca.crt.erb)config/peer.crt(fromconfig/peer.crt.erb)config/peer.key(fromconfig/peer.key.erb)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/ directory.