Thank you for opening your first issue here! 🛠

To address the issues with the flyte-core Helm chart, you can modify the values.yaml file to ensure ServiceAccounts are created for all necessary deployments and correct any misconfigurations. Here are the steps:

1. ServiceAccounts Configuration: Ensure that each deployment has the serviceAccount section properly configured in the values.yaml file. For example, for flyteadmin:

flyteadmin:
  serviceAccount:
    create: true
    name: flyteadmin

2. Fixing Warnings: Address the warning messages by ensuring that the values.yaml file does not have conflicting types for the same key. For example, ensure flyteagent.podEnv is correctly defined as a table if it is being overwritten.

3. Naming Conventions: Ensure consistent naming conventions across the Helm chart by standardizing the names used in the values.yaml file and the templates.

Would you like more detailed steps or code snippets for these configurations?

Sources:

• Flyte Helm Chart Values
• Flyte EKS Service Accounts
• Flyte Auth Configuration Issue

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

I have drafted proposed changes here:
#5362