-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathy-cluster-provision-minikube
executable file
·32 lines (25 loc) · 1.19 KB
/
y-cluster-provision-minikube
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
#!/usr/bin/env bash
[ -z "$DEBUG" ] || set -x
set -eo pipefail
YBIN="$(dirname $0)"
[ "$1" = "help" ] && echo '
Provision a cluster with minikube, currently hyperkit for OSX by default
' && exit 0
[ -z "$devcluster_driver" ] && devcluster_driver=hyperkit
[ -z "$devcluster_memory" ] && devcluster_memory=8192
[ -z "$devcluster_cpus" ] && devcluster_cpus=4
# enable-admission-plugins is from https://knative.dev/docs/install/knative-with-minikube/
y-minikube start \
--insecure-registry=builds-registry.ystack.svc.cluster.local \
--memory=$devcluster_memory \
--cpus=$devcluster_cpus \
--disk-size=40g \
--vm-driver=$devcluster_driver \
--kubernetes-version=v1.14.4 \
--bootstrapper=kubeadm \
--extra-config=apiserver.enable-admission-plugins="LimitRanger,NamespaceExists,NamespaceLifecycle,ResourceQuota,ServiceAccount,DefaultStorageClass,MutatingAdmissionWebhook" \
--extra-config=apiserver.service-node-port-range=444-32767
# Skaffold detects context name "minikube" and triggers local build behavior, but we want all clusters to be treated as remote
kubectl config delete-context ystack-minikube || true
kubectl config rename-context minikube ystack-minikube
kubectl create namespace ystack