Hi flyters, we are planning to run our flyte clust...
# flyte-deployment
b
Hi flyters, we are planning to run our flyte cluster on lambda cloud. lambda cloud is where we can rent GPU instances/clusters such as A10, A100, H100 etc., or even clusters. Can you please recommend a guide/method to set up Flyte with K8S??
a
Hey Murali I think the closest is this guide we used for on prem but it's extensible for "generic" K8s distribution https://github.com/davidmirror-ops/flyte-the-hard-way/tree/main/docs%2Fon-premises%2Fsingle-node Once Flyte is configured, this resource also covers how to access GPUs https://www.union.ai/docs/v1/flyte/deployment/flyte-configuration/configuring-access-to-gpus/ Let us know any question during the process
b
Thank you David. I will try the procedure
Hi, When you setup single binary flyte cluster(using https://github.com/davidmirror-ops/flyte-the-hard-way/tree/main/docs%2Fon-premises%2Fsingle-node), what is the location of localregistry, in sandbox, it was localhost:30000
Hi, I continued to have the authentication issue 1st with demo server, then with single binary installation. • I have created the script and attached to service account as suggested. Still see this issue. • I added registry_config in ImageSpec. what am I missing? 403 is also bit misleading. Resource exists in gitlab cotainer registry. Any help to move forward is appreciated.
Copy code
[2/2] currentAttempt done. Last Error: USER::Grace period [3m0s] exceeded|containers with unready status: [a7qlckn2cn4csnhtp86g-n0-1]|Back-off pulling image "registry.gitlab.com/xx/xx/ns-devops/python:3.11": ErrImagePull: failed to pull and unpack image "registry.gitlab.com/xxx/xx/ns-devops/python:3.11": failed to resolve reference "registry.gitlab.com/qvyon/gemini/ns-devops/python:3.11": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to <https://gitlab.com/jwt/auth?scope=repository%3Aqvyon%2Fgemini%2Fns-devops%2Fpython%3Apull&service=container_registry>: 403 Forbidden