Private discovery.etcd.io?

[Joseph Tam]

Hi all

thanks in advance for any advice.

For an internal offline network, is there a way to run a private discovery etcd instance? for most production use we won't have access to ping etcd.io and use it as the discovery mechanism

-joe

[Brandon Philips]

On Wed, Apr 1, 2015 at 10:45 AM, Joseph Tam <jtk...@gmail.com> wrote:
> For an internal offline network, is there a way to run a private discovery
> etcd instance? for most production use we won't have access to ping etcd.io
> and use it as the discovery mechanism

Yes, you can point it at an existing etcd cluster (for example a
single machine etcd cluster) or use DNS SRV records:

https://github.com/coreos/etcd/blob/master/Documentation/clustering.md#discovery

Thanks,

Brandon

[Joseph Tam]

Thank you, I am using a dedicated etcd as the private discovery and it works fine.

my next hurdle is now trying to use one generic cloud config file, since $private_ipv4 template function isn't available to me locally, what's the best approach to replace it with the pxe boot client ip (assume we are on dhcp)

-joe

#cloud-config

coreos:
  etcd:
    # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
    # specify the intial size of your cluster with ?size=X
    discovery: https://discovery.etcd.io/<token>
    # multi-region and multi-cloud deployments need to use $public_ipv4
    addr: $private_ipv4:4001
    peer-addr: $private_ipv4:7001