I'm using `flyte-binary` as a dependency in helm C...
# flyte-deployment
p
I'm using
flyte-binary
as a dependency in helm Chart. Name of my Chart is
flyte-backend
. Everything seems to work fine, I have registered a workflow successfully, created new project but when I try to do
pyflyte --remote
on my workflow, I get this error:
Copy code
Workflow[typing-project:development:workflows.digraphs_workflow.digraphs_workflow] failed. RuntimeExecutionError: max number of system retry attempts [11/10] exhausted. Last known status message: failed at Node[n0]. RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [container]: [InternalError] failed to create resource, caused by: Internal error occurred: failed calling webhook "flyte-pod-webhook.flyte.org": failed to call webhook: Post "https://flyte-binary-webhook.flyte.svc:443/mutate--v1-pod?timeout=10s": service "flyte-binary-webhook" not found
My webhook is called
flyte-backend-flyte-binary-webhook
, so I guess there is some problem with name resolution? I tried to call my Chart any other name, but webhook is still named
mychartname-flyte-binary-webhook
and flyte is then looking for
flyte-backend-flyte-binary-webhook
. Is there a workaround?
128 Views