New RunLLM response generated: >>>*# Question* Hi Flyte Community, I hope this message finds you well. I am currently in the process of deploying a Flyte cluster on my on-premises Kubernetes (K8s) setup, which consists of three nodes. I am following the guidelines outlined in this repository: [Flyte the Hard Way] (https://github.com/davidmirror-ops/flyte-the-hard-way). My goal is to utilize

Minio

and

PostgreSQL

for Flyte's storage needs. However, I have encountered an issue where, after applying the YAML configuration file using

kubectl

, the pods remain in a pending state instead of transitioning to running. I would greatly appreciate any insights or experiences from those who have faced similar challenges with on-prem K8s deployments. If anyone has suggestions or can share their expertise, it would be immensely helpful. Thank you in advance for your assistance! Best regards. # Answer To address pods stuck in a pending state, ensure that your Kubernetes nodes have sufficient resources and that the MinIO and PostgreSQL services are correctly configured. According to this discussion, check if the nodes have the necessary capacity and that there are no resource constraints. Additionally, verify that the storage configurations in your Flyte setup are correct, as mentioned in this GitHub issue. Would you like more details on troubleshooting this issue? Sources: - Flyte Deps Contour Envoy Pod Pending - Flyte MinIO Configuration Issue Slack Link https://.slack.com/archives/CP2HDHKE1/p1731500301.223749 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.