@@ -13,7 +13,8 @@ The examples below use the [tm](https://github.com/triggermesh/tm/releases/tag/v
1313To combine the runtime with your source, the examples below produce a new Docker image each time.
1414While these images can be considered temporary,
1515builds must be pushed to a Docker registry in order for Kubernetes to be able to pull.
16- In the ` tm ` commands below we use [ Knative Local Registry] ( https://github.com/triggermesh/knative-local-registry )
16+ By default ` tm ` uses [ Knative Local Registry] ( https://github.com/triggermesh/knative-local-registry )
17+ - equivalent to adding ` --registry-host knative.registry.svc.cluster.local ` to the commands below -
1718so that builds can run without registry authentication.
1819To use your own registry, replace ` --registry-host ` with secrets according to [ tm docs] ( https://github.com/triggermesh/tm#docker-registry ) .
1920
@@ -32,7 +33,6 @@ tm deploy service python-test -f https://github.com/serverless/examples \
3233 --build-template knative-python37-runtime \
3334 --build-argument DIRECTORY=aws-python-simple-http-endpoint \
3435 --build-argument HANDLER=handler.endpoint \
35- --registry-host knative.registry.svc.cluster.local \
3636 --wait
3737```
3838
@@ -63,7 +63,6 @@ tm deploy service node4-test -f https://github.com/serverless/examples \
6363 --build-template knative-node4-runtime \
6464 --build-argument DIRECTORY=aws-node-serve-dynamic-html-via-http-endpoint \
6565 --build-argument HANDLER=handler.landingPage \
66- --registry-host knative.registry.svc.cluster.local \
6766 --wait
6867```
6968
@@ -107,7 +106,6 @@ tm deploy buildtemplate -f https://raw.githubusercontent.com/triggermesh/knative
107106```
108107tm deploy service node-lambda -f . --build-template knative-node10-runtime \
109108 --build-argument HANDLER=handler.sayHelloAsync \
110- --registry-host knative.registry.svc.cluster.local \
111109 --wait
112110```
113111
0 commit comments