@ancient-wolf-19325, Below log is seen in flyteadmin and it is not starting, what am i missing here ? stow configuration section missing, defaulting to legacy s3/minio connection config

The log message "stow configuration section missing, defaulting to legacy s3/minio connection config" means FlyteAdmin did not find a

stow

section in your storage config and is falling back to the older

connection

-based S3/MinIO configuration. This is not necessarily an error, but it indicates your config is missing the recommended

stow

block for storage, which is now preferred for S3/MinIO backends. If FlyteAdmin is not starting, there may be a misconfiguration in your storage section, such as missing or incorrect keys like

access-key

,

secret-key

, or

endpoint

under

connection

or

stow

blocks, or the

container

(bucket) name is not set properly. See the flyteadmin_config.yaml example and storage config reference. Would you like more detail on how to structure your storage config for FlyteAdmin, or help troubleshooting startup errors? Sources: - flyteadmin_config.yaml - FlyteAdmin storage config reference 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.