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.

Hey @bitter-photographer-94114 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

I'm now using on-prem. Is there any way we can deploy on on-prem one?

yeah sure, but are you using

k3s

or how did you deploy your Kubernetes cluster?

It was already setup by our devops team. Do we need to know?

well, not exactly. Do you have access to run

kubectl

commands to your cluster?

Yes I have.

cool, can you do

kubectl get storageclass

It's saying- "no resource found".

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