Skip to content
This repository was archived by the owner on Dec 11, 2023. It is now read-only.

Commit bb44584

Browse files
committed
Evaluates tm's new registry options for KLR
1 parent 88afbdf commit bb44584

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,16 @@ With these templates, you can run your AWS Lambda functions **as is** in a Knati
88

99
The examples below use the [tm](https://github.com/triggermesh/tm/releases/tag/v0.0.7) CLI to interact with Knative but one could also use `kubectl`:
1010

11+
### Docker registry for builds
12+
13+
The examples below produce a new Docker image each time,
14+
that combines the runtime with the source.
15+
While these images can be considered temporary,
16+
bilds must push to a Docker registry in order for Kubernetes to be able to launch the container.
17+
In the `tm` commands below we use [Knative Local Registry](https://github.com/triggermesh/knative-local-registry)
18+
so that builds can run without registry authentication.
19+
To use your own registry, replace `--registry-host` with secrets according to [tm docs](https://github.com/triggermesh/tm#docker-registry).
20+
1121
### Python
1222

1323
1. Install buildtemplate
@@ -96,6 +106,7 @@ tm deploy buildtemplate -f https://raw.githubusercontent.com/triggermesh/knative
96106
```
97107
tm deploy service node-lambda -f . --build-template knative-node10-runtime \
98108
--build-argument HANDLER=handler.sayHelloAsync \
109+
--registry-host knative.registry.svc.cluster.local \
99110
--wait
100111
```
101112

0 commit comments

Comments
 (0)