kelseyhightower / kubestack Goto Github PK

@kelseyhightower would be nice to bootstrap master/ some nodes on GCE and some bare metal nodes too.

Any good ideas how to connect bare-metal worker / nodes back to GCE etcd cluster and k8s master?

It worked well for me with weave network, but might be you have some better ideas.

Would be good to provision master and node between different zones,
as to use one zone for the whole cluster is not a good idea.

For testing purposes it is fine, but people will start running production clusters :)

Would be handy to have support for:

1. standalone etcd cluster machines (useful to use for development clusters)
2. 3x etcd cluster
3. 5x etcd cluster

Can we also update systemd units without rebuilding image?
As destroying servers just for that is not a good idea I think :)

is any way to add metadata via packer?
so that could be handy to split in three groups (maybe separate image per server group):

1. etcd clusters machines
2. k8s master/s
3. nodes
   As right now I see only one easy way using fleet global units to do upgrades for
   systemd units, kubestack binaries and k8s version upgrade

@kelseyhightower I would advise to change /etc/kubestack-account.json to ~/kubestack/kubestack-account.json to store the file.

It is much easier to find and clean things up, no needs to put under main system /etc folder.

If you are happy with my suggestion, I can make all necessary changes and issue the PR for that.

How the kubestack binaries (etcd, fleetd, ect) are going to be updated?

We do not want to build a new image with Packer :)

Then we need to restart all units including k8s ones.

Hi @kelseyhightower, it looks like this http://storage.googleapis.com/kubestack/kubestack-0.17.1.tar.gz is missing, can I get it from other repo?

➜  packer git:(packer_fixs) ✗ wget -O kubestack.tar.gz http://storage.googleapis.com/kubestack/kubestack-0.17.1.tar.gz 
--2016-09-01 16:21:44--  http://storage.googleapis.com/kubestack/kubestack-0.17.1.tar.gz
Resolving storage.googleapis.com (storage.googleapis.com)... 64.233.190.128, 2800:3f0:4003:c01::80
Connecting to storage.googleapis.com (storage.googleapis.com)|64.233.190.128|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-09-01 16:21:45 ERROR 404: Not Found.

are CoreOS updates enabled?

Can the CoreUpdate be used?

Users should be able to change their hostnames to match their Google Compute Environment.

ability to pre-append to server names, so multiple clusters
can be run under the same project