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 Mar 13, 2021. It is now read-only.
> NOTE: If your Spring Boot application contains a single function bean, then you can omit the `--handler`options since the invoker is able to automatically detect it. You can also omit the `--handler` if the JAR manifest has a `Function-Class` entry.
151
+
> NOTE: If your Spring Boot application contains a single function bean, then you can omit the `--handler`flag since the invoker is able to automatically detect it. You can also omit the `--handler` flag if the JAR manifest has a `Function-Class` entry.
152
152
153
153
> NOTE: You need to provide a tag for the image to avoid Kubernetes trying to download the latest version of the image.
154
-
If the specified image tag already exists in the Docker daemon then Kubernetes will use it since `IfNotPresent` is the default pull policy.
154
+
The default pull policy is `IfNotPresent` which means that Kubernetes will always attempt to pull the latest image from the registry unless there is a tag specified.
155
155
156
156
Once the function is up and running you can invoke it using:
157
157
@@ -186,9 +186,10 @@ To build with a plain Java function, you can use:
> NOTE: If your Spring Boot application contains a single function bean, then you can omit the `--handler` options since the invoker is able to automatically detect it. You can also omit the `--handler` if the JAR manifest has a `Function-Class` entry.
193
194
194
195
> NOTE: It is possible to have multiple function beans in the same source repository and just refer to the one you want to use when creating the riff function using the `--handler` option.
0 commit comments