ea0978f4f2
This feature adds Juju provisioning to the kube-up script. It currently
parses out the pre-requisits on debian/ubuntu based systems and installs
them if they are missing.
From there we followed the integration path that was found in the
libvirt-coreos path, implementing the methods found in the boilerplate
and calling juju service calls. There are a few "arbitrary sleeps" in
the code to allow the cloud provider to settle and properly deploy.
These are work-around cases from the script executing faster than juju
was able to communicate from the state server to subsequent nodes. I
left comments inline at these points.
To exercise this:
export KUBERNETES_PROVIDER=juju
cluster/kube-up.sh
It will spin up a ref arch with 1 Kubernetes Master, 2 minions, and run
the cluster validation checks against the deployment. Bridging the gap
between the juju specific bits and the upstream recommended guides for
getting started with Juju.
To note, if you do not have a "current environment" set in Juju, it will
spin up the quickstart integration wizard in interactive mode, allowing
you to configure juju, and add the proper provider/use it. Otherwise it
assumes you're in the provider you wish to use, and will deploy there.
53 lines
2.1 KiB
Bash
53 lines
2.1 KiB
Bash
#!/bin/bash
|
|
|
|
# Copyright 2014 Google Inc. All rights reserved.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
# Set the default provider of Kubernetes cluster to know where to load provider-specific scripts
|
|
# You can override the default provider by exporting the KUBERNETES_PROVIDER
|
|
# variable in your bashrc
|
|
#
|
|
# The valid values: 'gce', 'gke', 'aws', 'azure', 'vagrant', 'vsphere', 'libvirt-coreos', 'juju'
|
|
|
|
KUBERNETES_PROVIDER=${KUBERNETES_PROVIDER:-gce}
|
|
|
|
# Some useful colors.
|
|
if [[ -z "${color_start-}" ]]; then
|
|
declare -r color_start="\033["
|
|
declare -r color_red="${color_start}0;31m"
|
|
declare -r color_yellow="${color_start}0;33m"
|
|
declare -r color_green="${color_start}0;32m"
|
|
declare -r color_norm="${color_start}0m"
|
|
fi
|
|
|
|
# Returns the server version as MMmmpp, with MM as the major
|
|
# component, mm the minor component, and pp as the patch
|
|
# revision. e.g. 0.7.1 is echoed as 701, and 1.0.11 would be
|
|
# 10011. (This makes for easy integer comparison in bash.)
|
|
function kube_server_version() {
|
|
local server_version
|
|
local major
|
|
local minor
|
|
local patch
|
|
|
|
# This sed expression is the POSIX BRE to match strings like:
|
|
# Server Version: &version.Info{Major:"0", Minor:"7+", GitVersion:"v0.7.0-dirty", GitCommit:"ad44234f7152e9c66bc2853575445c7071335e57", GitTreeState:"dirty"}
|
|
# and capture the GitVersion portion (which has the patch level)
|
|
server_version=$(${KUBECTL} --match-server-version=false version | grep "Server Version:")
|
|
read major minor patch < <(
|
|
echo ${server_version} | \
|
|
sed "s/.*GitVersion:\"v\([0-9]\{1,\}\)\.\([0-9]\{1,\}\)\.\([0-9]\{1,\}\).*/\1 \2 \3/")
|
|
printf "%02d%02d%02d" ${major} ${minor} ${patch} | sed 's/^0*//'
|
|
}
|