@@ -15,21 +15,17 @@ Why? Couple of reasons:
15
15
16
16
## Faking it
17
17
18
- If you don't want to actually run through the demo yourself but you'd still
19
- like to see what it looks like when you run it, simply clone this repo and
20
- run:
18
+ If you don't have an IKS cluster, don't have good internet connectivity,
19
+ or for whatever reason just don't want to actually execute all of the steps
20
+ of the demo but you'd still like to see what the demo looks like, simple run:
21
21
``` bash
22
22
$ USESAVED=1 ./demo
23
23
```
24
-
25
24
The demo will pause for each step, just press the spacebar to continue.
26
25
27
26
This will run the demo code but use the output from a saved run. The output
28
27
will look just like you're running it live.
29
28
30
- This is also good for cases where you don't have internet connectivity but
31
- still want to show it off.
32
-
33
29
## Demo Setup
34
30
35
31
This demo assumes you're using [ IBM's Kubernetes Service] ( cloud.ibm.com/iks )
@@ -51,16 +47,13 @@ No other special setup should be needed, so let's move on to the demo
51
47
52
48
You can run the demo manually or via the ` demo ` script.
53
49
54
- If you want to use the ` demo ` script make sure you set the ` DOMAIN `
55
- environment variable to the domain name of your IKS cluster first :
50
+ If you want to use the ` demo ` script, where it'll do all of the typing
51
+ for you but still execute the commands, just run :
56
52
57
53
``` bash
58
- $ export DOMAIN=...
54
+ $ ./demo
59
55
```
60
56
61
- You can get the proper value by looking at the ` Ingress Subdomain `
62
- value in the ` ibmcloud bx ks cluster-get CLUSTER ` output.
63
-
64
57
For those who want to run the demo manually, let's walk through each step
65
58
to explain what's going on.
66
59
@@ -207,7 +200,7 @@ of this new resource will kick off a Tekton execution of the referenced
207
200
` Task ` . So, let's do it:
208
201
209
202
``` bash
210
- $ kapply task.yaml
203
+ $ ./ kapply task.yaml
211
204
task.tekton.dev/build-push created
212
205
taskrun.tekton.dev/build-image created
213
206
```
@@ -267,7 +260,7 @@ newly created image that's stored in our local Docker Registry.
267
260
Let's create it:
268
261
269
262
``` bash
270
- $ kapply service.yaml
263
+ $ ./ kapply service.yaml
271
264
service.serving.knative.dev/hello created
272
265
```
273
266
@@ -290,11 +283,9 @@ curl -s http://hello-default.kntest.us-south.containers.appdomain.cloud
290
283
All done, so let's clean-up:
291
284
292
285
``` bash
293
- $ kubectl delete -f service.yaml
294
- $ kubectl delete -f hub.yaml
286
+ $ kubectl delete -f service.yaml -f hub.yaml
295
287
```
296
288
297
-
298
289
## Some Notes
299
290
300
291
As I mentioned previsously, I picked Docker's Registry for a couple of
0 commit comments