• Ketan (kumare3)

    Ketan (kumare3)

    1 month ago
  • a

    allen

    1 month ago
    Hey community, I’m trying to deploy Flyte on my company’s AWS infrastructure following this guide. We’ve installed AWS ELB Controller. The pods seem to be healthy in the cluster but the ingress is not getting assigned any address for
    flyteconsole
    due to the following error in the AWS ELB Controller logs:
    {
      "level": "error",
      "ts": 1659712067.8667307,
      "logger": "controller",
      "msg": "Reconciler error",
      "controller": "ingress",
      "name": "flyte",
      "namespace": "",
      "error": "InvalidParameter: 1 validation error(s) found.\n- minimum field value of 1, CreateTargetGroupInput.Port.\n"
    }
    Seems like the issue is https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1695 due to the service that the ingress routes to having type
    clusterip
    instead of
    nodeport
    , yet the helm chart for flyteconsole define the service as type
    clusterip
    . So I’m wondering if there’s something else that I’m not configuring correctly. If anyone else has run into something similar help would be very welcome! Thanks
    a
    Jacob Wang
    +2
    33 replies
    Copy to Clipboard
  • a

    Andrew Achkar

    1 month ago
    Q: I noticed the flyte-core helm charts reference reference the cr.flyte.org container registry, but there are also equivalent images stored in the github container registry (eg. https://github.com/flyteorg/flyteadmin/pkgs/container/flyteadmin). Is there any downside to referencing the images in github container register as compared to cr.flyte.org? Are those registries different in any way?
    a
    Samhita Alla
    2 replies
    Copy to Clipboard
  • s

    Shahwar Saleem

    1 month ago
    Hi Flyte Fellows, I have a question about Flytectl Auth. There are 2 major concerns when testing flytectl auth over Pkce which I will summarize in 🧵 :
    s
    Ketan (kumare3)
    +2
    37 replies
    Copy to Clipboard
  • Alireza

    Alireza

    1 month ago
    I am trying to deploy Flyte on AWS manually using our docs and at this step I got this error.
    % kubectl get pods --namespace default
    error: You must be logged in to the server (Unauthorized)
    Alireza
    Shivay Lamba
    7 replies
    Copy to Clipboard
  • e

    Edgar Trujillo

    1 month ago
    Can a multi-cluster Flyte deployment be configured to schedule pods to different clusters based on
    domains
    versus
    labels
    like shown in the example
    configmap
    ? https://docs.flyte.org/en/latest/deployment/multicluster.html
    e
    Ketan (kumare3)
    9 replies
    Copy to Clipboard
  • Alireza

    Alireza

    1 month ago
    I am trying to deploy Flyte on AWS manually using our docs after running
    curl -sL <https://raw.githubusercontent.com/flyteorg/flyte/master/charts/flyte-core/values-eks.yaml>
    It is asking for redis info:
    redisHostUrl: <REDIS_HOST_URL>
      redisHostKey: <REDIS_HOST_KEY>
    Alireza
    Ketan (kumare3)
    +2
    4 replies
    Copy to Clipboard
  • Rahul Mehta

    Rahul Mehta

    4 weeks ago
    Is this line in the docs correct? https://docs.flyte.org/en/latest/deployment/cluster_config/general.html
    In the absence of an override, the global default values in the FlyteAdmin config are used.
    https://github.com/flyteorg/flyte/blob/1e3d515550cb338c2edb3919d79c6fa1f0da5a19/charts/flyte-core/values.yaml#L35,L43 this looked like the resource requests/limits for the flyteadmin pods themselves, is flyte actually using those as the defaults for tasks? I just tried updating
    task_resource_defaults
    in the helm chart w/ new limits and I didn't see the change reflected in the configmap after applying the changes to the cluster
    Rahul Mehta
    k
    19 replies
    Copy to Clipboard
  • s

    Shahwar Saleem

    3 weeks ago
    Hi Team, Has anyone seen this while issuing
    helm install
    ?
    Error: file '/Users/shahwar.saleem/Library/Caches/helm/repository/flyte-core-v1.1.0.tgz' does not appear to be a gzipped archive; got 'application/octet-stream'
    s
    k
    +2
    16 replies
    Copy to Clipboard