@ancient-wolf-19325 I am deploying Flyte using the flyte-core Helm chart. I would like a seed project of specific name to be created on deployment. I have set the

flyteadmin.initialProjects

value, but nothing happens. Is there anything more needed?

To create a seed project during Flyte deployment using the

flyte-core

Helm chart, you need to set the

flyteadmin.initialProjects

value in your

values.yaml

file. Ensure that the

flyteadmin.enabled

is set to

true

and the

initialProjects

list contains the desired project names. Example

values.yaml

configuration:

flyteadmin:
  enabled: true
  initialProjects:
    - my_custom_project

Make sure that the

initialProjects

key is correctly indented and placed under the

flyteadmin

section. This configuration should trigger the creation of the specified projects during the deployment process. If the projects are still not being created, verify that the FlyteAdmin service is correctly configured and running. You can check the logs of the FlyteAdmin pod for any errors related to project creation. Would you like more details on troubleshooting this issue? Sources: - flyte-core values.yaml - Deployment YAML 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 how can I increas log level of flyteadmin if I deploy using flyte-core chart?

To increase the log level of FlyteAdmin when deploying using the

flyte-core

Helm chart, you need to set the

logger.level

in the FlyteAdmin configuration. This can be done by adding the appropriate configuration in your

values.yaml

file. Example

values.yaml

configuration:

flyteadmin:
  enabled: true
  extraArgs:
    - --logger.level=6

This configuration sets the log level to 6, which is the most verbose level. Ensure that the

extraArgs

key is correctly indented and placed under the

flyteadmin

section. Would you like more details on this configuration? Sources: - FlyteAdmin logging configuration 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 How does the above relate to setting

logger.level

in the

core

section of Helm values?

Setting the

logger.level

in the

core

section of the Helm values is another way to configure the logging level for FlyteAdmin. This approach involves directly modifying the FlyteAdmin configuration within the

core

section of the

values.yaml

file. Example

values.yaml

configuration:

configuration:
  core:
    logger:
      level: 6

This configuration sets the log level to 6 for the core FlyteAdmin service. Ensure that the

logger.level

key is correctly indented and placed under the

core

section. Both methods (using

extraArgs

and setting

logger.level

in the

core

section) achieve the same goal of increasing the log level for FlyteAdmin. However, using

extraArgs

is more specific to command-line arguments, while setting

logger.level

in the

core

section is more integrated into the FlyteAdmin configuration. Would you like more details on these configurations? Sources: - https://discuss.flyte.org/t/8579436/hi-community-i-tried-to-integrate-self-hosted-gitlab-as-an-e/ - https://discuss.flyte.org/t/2176456/hi-question-on-logging-i-m-running-on-gcp-configured-using-o/ 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.