forked from NearNodeFlash/nnf-dm
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdeploy.sh
executable file
·66 lines (58 loc) · 2.1 KB
/
deploy.sh
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
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
#!/bin/bash
# Copyright 2021-2023 Hewlett Packard Enterprise Development LP
# Other additional copyright holders may be indicated within.
#
# The entirety of this work is 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.
# Deploy controller to the K8s cluster specified in ~/.kube/config.
usage() {
cat <<EOF
Deploy or Undeploy Data Movement
Usage $0 COMMAND KUSTOMIZE [IMG] [NNFMFU_IMG]
Commands:
deploy Deploy data movement
undeploy Undeploy data movement
EOF
}
CMD=$1
KUSTOMIZE=$2
IMG=$3
NNFMFU_IMG=$4
case $CMD in
deploy)
(cd config/manager &&
$KUSTOMIZE edit set image controller="$IMG" &&
$KUSTOMIZE edit set image nnf-mfu="$NNFMFU_IMG")
$KUSTOMIZE build config/default | kubectl apply -f - || true
# Sometimes the deployment of the DataMovementManager occurs too quickly for k8s to digest the CRD
# Retry the deployment if this is the case. It seems to be fast enough where we can just
# turn around and re-deploy; but this may need to move to a polling loop if that goes away.
echo "Waiting for DataMovementManager resource to become ready"
while :; do
[[ $(kubectl get datamovementmanager -n nnf-dm-system 2>&1) == "No resources found" ]] && sleep 1 && continue
$KUSTOMIZE build config/default | kubectl apply -f -
break
done
;;
undeploy)
# When the DataMovementManager CRD gets deleted all related resource are also
# removed, so the delete will always fail. We ignore all errors at our
# own risk.
$KUSTOMIZE build config/default | kubectl delete --ignore-not-found -f -
;;
*)
usage
exit 1
;;
esac