Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By Louis Lobban
Hi There,
I have attempted to setup a CoreOS Cluster using 3 DigitalOcean droplets across various Datacentres. When I input “fleetctl list-machines” into the leader container (LDN1) it gives the following response:
core@ldn1 ~ $ fleetctl list-machines
MACHINE IP METADATA
035d1637… 178.62.107.22 host=LDN1,location=lon1,public_ip=178.62.10*.**,region=lon
0c948a60… 128.199.55.158 host=AMS1,location=ams3,public_ip=128.199.5*.*,region=ams ** My issue here is that it is not displaying my New York container, using the same Discovery URL as the others, yet when I input "curl -L http://127.0.0.1:4001/v2/stats/leader it shows the NY container:
core@ldn1 ~ $ curl -L http://127.0.0.1:4001/v2/stats/leader
{“leader”:“LDN1”,“followers”:{“AMS1”:{“latency”:{“current”:8.961378,“average”:9. 948075820900373,“standardDeviation”:1.6590218277732314,“minimum”:8.478871,“maxim um”:52.14463},“counts”:{“fail”:0,“success”:6220}},“NYC1”:{“latency”:{“current”:0 ,“average”:0,“standardDeviation”:0,“minimum”:9.223372036854776e+18,“maximum”:0},
If anybody can shed some light on this it would be greatly appreciated! I’ve been here since 9 trying to configure this correctly and it’s starting to get a bit tedious.
Kind Regards, Louis