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
When a function is newly deployed or updated folks will see a few
connection refused errors in their XR. This setting may help with that
by telling Crossplane to wait for the function to become ready rather
than immediately returning an error.
This commit also removes the 10 second timeouts for dialing and running
a function. gRPC no longer recommends using DialContext. Instead they
recommend using NewClient, which doesn't actually create a connection
and thus doesn't need a timeout.
Instead of a 10 second timeout to run the function, RunFunction now just
uses the parent context's timeout which happens to be 2 minutes. This
means the entire function pipeline (technically the entire XR reconcile)
must complete within 2 minutes. This allows some functions to take a bit
longer as long as the total runtime is within the timeout.
Signed-off-by: Nic Cope <[email protected]>
conn, err:=grpc.DialContext(ctx, active.Status.Endpoint,//nolint:staticcheck // Figure out how to replace deprecated grpc.DialContext with grpc.NewClient and still pass the dialFunctionTimeout.
0 commit comments