airship/airshipctl
Code Issues Proposed changes

Move kubectl calls to KRM toolbox pt.7

Browse Source 
Move kubectl calls to phases. These phases call KRM toolbox with
prepared shell scripts.

Change-Id: If847bc822981f4781eed12461f16adfbf53686a6
Relates-To: #517
This commit is contained in:
Vladislav Kuzmin 2021-05-17 14:52:36 +04:00
parent 22b84b2ca0
commit dff6085f34
1 changed files with 8 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
tools/deployment/34_deploy_controlplane_target.sh
View File

@ -14,24 +14,17 @@
set -ex
export KUBECONFIG=${KUBECONFIG:-"$HOME/.airship/kubeconfig"}
export KUBECONFIG_TARGET_CONTEXT=${KUBECONFIG_TARGET_CONTEXT:-"target-cluster"}
echo "Create target k8s cluster resources"
airshipctl phase run controlplane-target --debug
echo "List all nodes in target cluster"
kubectl \
--kubeconfig $KUBECONFIG \
--context $KUBECONFIG_TARGET_CONTEXT \
--request-timeout 10s \
get node
# Scripts for this phase placed in manifests/function/phase-helpers/wait_node/
# To get ConfigMap for this phase, execute `airshipctl phase render --source config -k ConfigMap`
# and find ConfigMap with name kubectl-get-node
airshipctl phase run kubectl-get-node-target --debug
echo "List all pods in target cluster"
kubectl \
--kubeconfig $KUBECONFIG \
--context $KUBECONFIG_TARGET_CONTEXT \
--request-timeout 10s \
get pods \
--all-namespaces
# Scripts for this phase placed in manifests/function/phase-helpers/get_pods/
# To get ConfigMap for this phase, execute `airshipctl phase render --source config -k ConfigMap`
# and find ConfigMap with name kubectl-get-pods
airshipctl phase run kubectl-get-pods-target --debug