Summary
The user is deploying a Flyte cluster on their on-premises Kubernetes setup with three nodes, utilizing Minio and PostgreSQL for storage. They are facing an issue where the pods remain in a pending state after applying the YAML configuration file with kubectl. The user seeks insights or suggestions from the community about similar challenges in on-prem K8s deployments and requests a brief step-by-step guide or reference for the setup, noting that the storage class is functioning correctly.
kylee.knight
kubectl get storageclass working fine. but still the same issue.
kylee.knight
I'm still confused about it a little. Can you share any brief step by step guide or reference to do setup on my side?
david.espejo
this is covered at the first section of this page: https://github.com/davidmirror-ops/flyte-the-hard-way/blob/main/docs/on-premises/single-node/002-single-node-onprem-install.md#configure-dependencies-and-install-flyte|https://github.com/davidmirror-ops/flyte-the-hard-way/blob/main/docs/on-premises/single-node/002-single-node-onprem-install.md#configure[…]all-flyte
david.espejo
ok so that's part of the problem. The manifests in that repo are configured to request a volume from whatever Storage Class you're using as default
kylee.knight
It's saying- "no resource found".
david.espejo
cool, can you do kubectl get storageclass
kylee.knight
Yes I have.
david.espejo
well, not exactly. Do you have access to run kubectl commands to your cluster?
kylee.knight
It was already setup by our devops team. Do we need to know?
david.espejo
yeah sure, but are you using k3s or how did you deploy your Kubernetes cluster?
kylee.knight
I'm now using on-prem. Is there any way we can deploy on on-prem one?
david.espejo
Hey <@U0789L35QGL>
What Kubernetes distro are you using?
I suspect if your pods are Pending it's because the request to provision and mount storage (aka Persistent Volume Claim) isn't being fulfilled. For that to work it needs a Storage Class that comes from a storage provisioner. This is covered in the tutorial for a k3s deployment but not for other distros
kylee.knight
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.