5881ba43f8
Putting contiv etcd and etcd-proxy into the same daemonset and manage the difference by a env file is not good for scaling (adding nodes). This commit split them into two daemonsets so that when adding nodes, k8s could automatically starting a etcd-proxy on new nodes without need to run related play that putting env file.
9 lines
422 B
Django/Jinja
9 lines
422 B
Django/Jinja
# contiv etcd config
|
|
export ETCD_DATA_DIR=/var/lib/etcd/contiv-data
|
|
export ETCD_ADVERTISE_CLIENT_URLS={{ contiv_etcd_ad_urls }}
|
|
export ETCD_INITIAL_ADVERTISE_PEER_URLS={{ contiv_etcd_peer_urls }}
|
|
export ETCD_LISTEN_PEER_URLS={{ contiv_etcd_peer_urls }}
|
|
export ETCD_LISTEN_CLIENT_URLS={{ contiv_etcd_listen_urls | join(",") }}
|
|
export ETCD_NAME={{ contiv_etcd_name }}
|
|
export ETCD_INITIAL_CLUSTER={{ contiv_etcd_endpoints }}
|