seunggs

    seunggs

    2 months ago
    p

    Prafulla Mahindrakar

    2 months ago
    For the 501 issue : Do you see an entry in your ingress
    kubectl get ingress -n flyte -o yaml
    - backend:
                service:
                  name: flyteadmin
                  port:
                    number: 80
              path: /me
              pathType: ImplementationSpecific
    Also this only is backed by service currently if auth is enabled. https://github.com/flyteorg/flyteadmin/blob/2a216f5684360f3e68b3130bc5057f4d3a4466b3/pkg/server/service.go#L256 ORhttps://github.com/flyteorg/flyteadmin/blob/2a216f5684360f3e68b3130bc5057f4d3a4466b3/pkg/server/service.go#L359 So if you don’t have auth enabled then you can ignore the error . But you can create a issue to avoid calling this API. For the 404 issue : This is an expected error if you dont have an overriden workfexecutionConfig for flytexamples/development
    seunggs

    seunggs

    2 months ago
    OK I don’t have auth enabled so I guess
    /me
    error is expected then. Can you elaborate on 404 issue a little? What is
    workfexecutionConfig
    ?
    Thank you by the way for your help!
    p

    Prafulla Mahindrakar

    2 months ago
    It provides a way to define common execution attributes for all your workflows with a project/domain https://docs.flyte.org/projects/flyteidl/en/latest/protos/docs/admin/admin.html#ref-flyteidl-admin-workflowexecutionconfig How this can be updated using the cli https://docs.flyte.org/projects/flytectl/en/latest/gen/flytectl_update_workflow-execution-config.html eg : Security context for all your workflows running under flytexamples/development can use configured service account in the workflow execution config. You can additionally override it during launch which takes a higher precedence
    seunggs

    seunggs

    2 months ago
    Oh I see - so this is limited to a single project/domain combination though?
    p

    Prafulla Mahindrakar

    2 months ago
    yes
    seunggs

    seunggs

    2 months ago
    OK - this is helpful thank you! Just one last thing - what is that react_devtools_backend error?
    p

    Prafulla Mahindrakar

    2 months ago
    That seems to be UI not handling the not found error .
    seunggs

    seunggs

    2 months ago
    Oh OK so it looks like these errors are expected based on my default setup - I just wanted to confirm to make sure it’s not affecting the core flyte workflows/tasks
    p

    Prafulla Mahindrakar

    2 months ago
    seunggs

    seunggs

    2 months ago
    Thank you so much for answering my questions!