8a48a74103
Not every cluster can be validated the same way. Factoring out the validate-cluster call into a kube-util.sh function allows customization. This allows to proceed with GoogleCloudPlatform/kubernetes#10049 before the mid/long-term unified cluster validation in GoogleCloudPlatform/kubernetes#11908 is implemented. Otherwise, the later blocks the former.
47 lines
1.3 KiB
Bash
Executable File
47 lines
1.3 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# Copyright 2014 The Kubernetes Authors 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.
|
|
|
|
# Bring up a Kubernetes cluster.
|
|
#
|
|
# If the full release name (gs://<bucket>/<release>) is passed in then we take
|
|
# that directly. If not then we assume we are doing development stuff and take
|
|
# the defaults in the release config.
|
|
|
|
set -o errexit
|
|
set -o nounset
|
|
set -o pipefail
|
|
|
|
KUBE_ROOT=$(dirname "${BASH_SOURCE}")/..
|
|
source "${KUBE_ROOT}/cluster/kube-env.sh"
|
|
source "${KUBE_ROOT}/cluster/kube-util.sh"
|
|
|
|
echo "... Starting cluster using provider: $KUBERNETES_PROVIDER" >&2
|
|
|
|
echo "... calling verify-prereqs" >&2
|
|
verify-prereqs
|
|
|
|
echo "... calling kube-up" >&2
|
|
kube-up
|
|
|
|
echo "... calling validate-cluster" >&2
|
|
validate-cluster
|
|
|
|
echo -e "Done, listing cluster services:\n" >&2
|
|
"${KUBE_ROOT}/cluster/kubectl.sh" cluster-info
|
|
echo
|
|
|
|
exit 0
|