File: MultipleDeployments.md

package info (click to toggle)
kustomize 5.8.0%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,608 kB
  • sloc: makefile: 162; sh: 123
file content (152 lines) | stat: -rw-r--r-- 4,047 bytes parent folder | download | duplicates (3)
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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
[kind]: https://github.com/kubernetes-sigs/kind

# Demo: Multiple Deployments

This demo helps you to multiple services on same kubenetes cluster using kustomize.

Steps:
1. Create the resources files for wordpress service.
2. Create the resources files for mysql service.
3. Spin-up kubernetes cluster on local using [kind].
4. Deploy the wordpress app using kustomize and verify the status.
5. Deploy the mysql app using kustomize on same "kind" cluster and verify the status.
6. Add and remove a resource to mysql service and verify prune.

First define a place to work:

<!-- @makeWorkplace @testE2EAgainstLatestRelease -->
```
DEMO_HOME=$(mktemp -d)
```

Alternatively, use

> ```
> DEMO_HOME=~/hello
> ```

## Establish the base

<!-- @createBase @testE2EAgainstLatestRelease -->
```
BASE=$DEMO_HOME/base
mkdir -p $BASE
OUTPUT=$DEMO_HOME/output
mkdir -p $OUTPUT

mkdir $BASE/wordpress
mkdir $BASE/mysql

curl -s -o "$BASE/wordpress/#1.yaml" "https://raw.githubusercontent.com\
/kubernetes-sigs/kustomize\
/master/examples/wordpress/wordpress\
/{deployment,kustomization,service}.yaml"

curl -s -o "$BASE/mysql/#1.yaml" "https://raw.githubusercontent.com\
/kubernetes-sigs/kustomize\
/master/examples/wordpress/mysql\
/{secret,deployment,kustomization,service}.yaml"
```

Create a `grouping.yaml` resource. By this, you are defining the grouping of the current directory, `mysql`. Kustomize uses the unique label in this file to track any future state changes made to this directory. Make sure the label key is `kustomize.config.k8s.io/inventory-id` and give any unique label value and DO NOT change it in future.
<!-- @createGroupingYaml @testE2EAgainstLatestRelease-->
```
cat <<EOF >$BASE/mysql/grouping.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: inventory-map
  labels:
    kustomize.config.k8s.io/inventory-id: mysql-app
EOF
```

Delete any existing kind cluster and create a new one. By default the name of the cluster is "kind"
<!-- @deleteAndCreateKindCluster @testE2EAgainstLatestRelease -->
```
kind delete cluster
kind create cluster
```

Let's run the wordpress and mysql services.
<!-- @RunWordpressAndMysql @testE2EAgainstLatestRelease -->
```
export KUSTOMIZE_ENABLE_ALPHA_COMMANDS=true

kustomize resources apply $BASE/mysql --status;

status=$(mktemp);
kustomize status fetch $BASE/mysql > $OUTPUT/status

test 1 == \
  $(grep "mysql" $OUTPUT/status | grep "Deployment is available. Replicas: 1" | wc -l); \
  echo $?

test 1 == \
  $(grep "mysql-pass" $OUTPUT/status | grep "Resource is always ready" | wc -l); \
  echo $?

test 1 == \
  $(grep "mysql" $OUTPUT/status | grep "Service is ready" | wc -l); \
  echo $?

kustomize resources apply $BASE/wordpress --status;

status=$(mktemp);
kustomize status fetch $BASE/wordpress > $OUTPUT/status

test 1 == \
  $(grep "wordpress" $OUTPUT/status | grep "Deployment is available. Replicas: 1" | wc -l); \
  echo $?

test 1 == \
  $(grep "wordpress" $OUTPUT/status | grep "Service is ready" | wc -l); \
  echo $?
```

Let's replace the secret resource from mysql service and verify prune and addition of resource.
<!-- @ReplaceResourceInMysql @testE2EAgainstLatestRelease -->

```
cat <<EOF >$BASE/mysql/secret2.yaml
apiVersion: v1
kind: Secret
metadata:
  name: mysql-pass2
type: Opaque
data:
  # Default password is "admin".
  password: YWRtaW5=
EOF

rm $BASE/mysql/secret.yaml

sed -i.bak 's/secret/secret2/' \
    $BASE/mysql/kustomization.yaml

sed -i.bak 's/mysql-pass/mysql-pass2/' \
    $BASE/mysql/deployment.yaml

kustomize resources apply $BASE/mysql --status;

status=$(mktemp);
kustomize status fetch $BASE/mysql > $OUTPUT/status

test 1 == \
  $(grep "mysql" $OUTPUT/status | grep "Deployment is available. Replicas: 1" | wc -l); \
  echo $?

test 1 == \
  $(grep "mysql-pass2" $OUTPUT/status | grep "Resource is always ready" | wc -l); \
  echo $?

test 1 == \
  $(grep "mysql" $OUTPUT/status | grep "Service is ready" | wc -l); \
  echo $?
```

Clean-up the cluster 
<!-- @deleteKindCluster @testE2EAgainstLatestRelease -->
```
kind delete cluster
```