Greetings, As some of you may know the new-workloads eco team has been working dilligently with Google upstream to land Juju as an officially supported provider in the Kubernetes project. We've just officially landed our first code PR that enables juju in the cluster-up (the official kubernetes deployment scripts)
https://github.com/GoogleCloudPlatform/kubernetes/pull/5414 I'm very proud to announce we are now ready to start iterating faster, and landed more features against the kubernetes charms than before. We are excited and looking to a great future being included in the upstream repository. Currently this will deploy the 0.8.1 release of juju, and can be accomplished by: cloning the kubernetes project export KUBERNETES_PROVIDER=juju cluster/kube-up.sh This will fire up juju-quickstart to populate details if there is no current-environment file in $JUJU_HOME. The rest is a fully automated deployment of the k8's charms to setup a micro-cluster consisting of 1 master, and 2 minions. If you try this and have any feedback we welcome it at the bundle repository https://github.com/whitmo/bundle-kubernetes Additionally we have a full fledge documentation suite setup here: http://whitmo.github.io/bundle-kubernetes/ All the best, Charles Butler <[email protected]> - Juju Charmer Come see the future of datacenter orchestration: http://jujucharms.com
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
