You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 7, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -3,14 +3,14 @@
3
3
4
4
This project provides a Kubernetes Operator for managing a `JSFunction`
5
5
custom resource. A `JSFunction` accepts a JavaScript function inline,
6
-
as well as an optional inline pakcage.json.
6
+
as well as an optional inline package.json.
7
7
8
8
When a `JSFunction` resource is applied to a cluster,
9
9
the controller takes the following steps during reconciliation.
10
10
11
11
* Check to see if a Knative `Service` for this function exists. If not, create one.
12
12
* Create a `ConfigMap` containing with the user supplied data (index.js/package.json)
13
-
* Create a `TaskRun`, installing any dependencies and building a runtime image using [`lanceball/js-runtime`](https://github.com/openshift-cloud-functions/faas-js-runtime-image)
13
+
* Create a `TaskRun`, installing any dependencies and building a runtime image using [`openshift-cloud-functions/faas-js-runtime-image`](https://github.com/openshift-cloud-functions/faas-js-runtime-image)
14
14
* Create a `PodSpec` for the `Service` specifying the runtime image just created
15
15
* Wires up knative eventing, if `events` is set to `true` in a `JSFunction` custom resource.
16
16
Knative Eventing objects `Subscription` and `Channel` are created and acts as a sink for the function.
0 commit comments