F

Flyte enables you to build & deploy data & ML pipelines, hassle-free. The infinitely scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks. Explore and Join the Flyte Community!

Guidance on GKE Node and Namespace Selection

Summary

The user is seeking guidance on selecting a specific GKE node and namespace for running workflows on Flyte, focusing on node affinity with Pod Templates and the rationale for node selection, particularly for GPU usage. They mention that Flyte creates a namespace for each project-domain and highlight the ability to specify a namespace in the Helm chart using namespace_mapping. The user wants to run on a standard node as requested by a client and is inquiring about documentation for namespace_mapping and the installation method of Flyte, questioning whether it was installed using flyte-binary or flyte-core. They also provide an example configuration for namespace_mapping and reference a previous inquiry about creating workflows with node selectors in GKE, which included instructions for configuring FlytePropeller and defining tasks with node selectors.

Status
resolved
Tags
    Source
    #ask-the-community