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
Well, my answer wouldn't be easy. So, the following env var needs to be set in docker run for API node. By itself, this env var represents a public (reachable through the internet) IP address of the LB container.
So, missing steps here are:
Deploy API container at the end.
When LB container deployed - check its IP address (that could be docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' <lb-container>).
The most crucial part here is Fn CLI simple test. Since this type of the deployment is not usual to anyone expect us, you need to show the following things:
Create a new context with API container IP address.
Deploy hello-world.
Inspect a function, highlight the annotation because it would be different compared to regular annotation you'd get from FN running throughfn start.
Call a function with both an HTTP trigger and invoke.
Pool runner doc misses
FN_PUBLIC_LB_URL
configuration which makes the deployment broken.The text was updated successfully, but these errors were encountered: