@ancient-wolf-19325 Flyte can't seem to log in to access the database I stood up via the Bitnami Postgres Helm Chart. I created a db called

flyteadmin

and I passed the same password that let me log in from my laptop.

Ensure the password is correctly set in the Kubernetes secret and referenced in Flyte's configuration. According to this discussion, you can create a Kubernetes secret for the database password and reference it in the

values.yaml

file. Verify the secret is correctly mounted and accessible by Flyte. Would you like more detail on setting up the secret or troubleshooting steps? Sources: - Flyte Discussion on Secrets 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@crooked-vase-16428 how did you install Flyte? I mean, what Helm chart?

@average-finland-92144 This one! https://docs.flyte.org/en/latest/deployment/deployment/cloud_simple.html#deployment-deployment-cloud-simple

https://github.com/davidmirror-ops/flyte-the-hard-way/blob/main/docs%2Faws%2F04-create-database.md This page includes a step to check db connection from inside the EKS cluster, could you check? What's the error message?

@average-finland-92144 I don't have it handy but it was about the password specifically.

And it works from your laptop?

Yep!

Can you share your

eks-starter.yaml

?

I don't have permissions on RDS, I had to stand up the Postgres server in the EKS cluster itself with this: https://github.com/bitnami/charts/tree/main/bitnami/postgresql/

Ah right sorry

gonna try setting the

global.postgresql.auth.database

param to

flyteadmin

. Before I was just logging in to postgres and doing

create database flyteadmin

Awesome!

@average-finland-92144 btw, should the

Getting Started

link in this line lead to the docs for

unittest

? Cuz they do right now (from here: https://docs.flyte.org/en/latest/deployment/deployment/cloud_simple.html#deployment-deployment-cloud-simple )

From here, you should be able to run through the Getting Started examples again. Save a backup copy of your existing configuration if you have one and generate a new config with

flytectl

.

Oh no, that's a problem Please file an issue

Thanks! Issue btw: https://github.com/flyteorg/flyte/issues/5892

The error you're encountering,

FlyteSystemUnavailableException

, suggests that the Flyte cluster is not accessible for remote execution. This could be due to several reasons, such as network misconfiguration or incorrect endpoint settings. According to this GitHub issue, similar errors often occur when the MinIO service or other storage backends are not correctly configured or accessible. To resolve this, ensure that your Flyte configuration file (

~/.flyte/config.yaml

) is correctly set up with the appropriate endpoint and storage settings. Verify that the MinIO or other storage service is running and accessible from your client machine. Additionally, check that the Flyte cluster is fully operational and that all necessary services are running without errors. Would you like more details on configuring Flyte or troubleshooting this issue? Sources: - this GitHub issue 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 I set

insecure: true

in

.flyte/config.yaml

but I'm still getting

*RuntimeError:* Failed to get signed url

Setting

insecure: true

in your

.flyte/config.yaml

allows connections without SSL verification, but the

RuntimeError: Failed to get signed url

indicates a potential issue with the storage configuration or network access to the storage service. According to this GitHub issue, such errors can occur if the MinIO service or other storage backends are not correctly configured or accessible. Ensure that the

storage.connection.endpoint

in your configuration file points to the correct MinIO service endpoint and that the service is accessible from your client machine. Verify that the MinIO service is running and that there are no network restrictions preventing access. Additionally, check that the Flyte cluster is fully operational and that all necessary services are running without errors. Would you like more details on configuring Flyte or troubleshooting this issue? Sources: - this GitHub issue 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 I'm not using

MinIO

, I'm following the

Single Cluster Simple Cloud Deployment

tutorial

If you're following the

Single Cluster Simple Cloud Deployment

tutorial and not using MinIO, the

Failed to get signed url

error might be related to the configuration of your cloud storage service. According to this GitHub issue, such errors can occur if the storage backend is not correctly configured or accessible. Ensure that your

.flyte/config.yaml

file is correctly set up with the appropriate cloud storage service endpoint and credentials. Verify that the storage service is accessible from your Flyte deployment and that there are no network restrictions preventing access. Additionally, check that the Flyte cluster is fully operational and that all necessary services are running without errors. Would you like more details on configuring Flyte or troubleshooting this issue? Sources: - this GitHub issue 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 I'm tryin to use S3 as the

storage

- I put a bucket in the

metadataContainer

and

userDataContainer

parameters, and this for the rest

provider: s3
    providerConfig:
      s3:
        region: "us-west-2"
        authType: "iam"

To use S3 as the storage backend in Flyte, ensure that your configuration is correctly set up with the necessary IAM roles and permissions. According to this discussion, you need to ensure that the IAM role associated with your Flyte deployment has the necessary permissions to access the specified S3 buckets. Make sure that the IAM role has permissions for actions like

s3:GetObject

,

s3:PutObject

, and

s3:ListBucket

on the specified buckets. Additionally, verify that the

providerConfig

in your Flyte configuration file is correctly set up with the appropriate region and authentication type. Would you like more details on configuring Flyte with S3 or troubleshooting this issue? Sources: - this discussion 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.