# Architecture Overview Neurox is architected in such a way that the Control plane components and the Workload management components can be deployed separately to different Kubernetes clusters due to infrastructure or networking constraints. ## Control plane cluster * Where GPU workloads are configured/managed * Communicates with all of its joined Workload clusters * Requires ingress and persistent disk * Hosts the endpoints for web access to the Neurox Control Portal ## Workload management cluster * Where GPU workloads run * Communicates with its control cluster * Does not require ingress * Does not require persistent disk * Directly interacts with the Kubernetes API ## Components These are the components of each type of cluster. ### Control plane cluster * *Portal*: Hosts the web app * *API*: Endpoint for web app requests * *Redis*: Persists Workload and configuration data * *Thanos*: Receives and aggregates metrics from all Workload clusters * *Relay Server*: Manages the secure connections from Workload clusters * *Authentication Server*: Manages user sessions * *Identity Provider Connector*: Manages user authentication ### Workload management cluster * *Workload Manager*: Directly manages GPU workloads running in Kubernetes * *Agent*: Collects GPU metrics * *Prometheus*: Forwards metrics to the Control cluster * *Relay Client*: Establishes a secure connection to the Control cluster --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.neurox.com/architecture/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.