> For the complete documentation index, see [llms.txt](https://campus-rover.gitbook.io/lab-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://campus-rover.gitbook.io/lab-notebook/fiiva/vnc-cluster/operation-guide/architecture.md).

# architecture.md

## Overview

The cloud desktop architecture is simple. On a high level, it looks like this:

![Overview](https://4196336753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LULg3WmBk4r0dWAdK9A%2Fuploads%2Fgit-blob-fa89c2967b50604be0772de1b8b74d476a473b8f%2Farch-overview.svg?alt=media)

## Cloud Desktop Cluster

Cloud desktop cluster is a cluster of cloud desktops. It is implemented as a K8s cluster for easy scheduling and orchestration of cloud desktop containers.

## Cloud Desktop Container

The cloud desktop container provides a virtualized desktop environment that is isolated and portable. It consists of 3 components.

* VNC server paired with a NoVNC server
* VSCode server
* Tailscale client

For details, see [Container Image](https://github.com/campusrover/labnotebook/blob/master/VNC-cluster/operation-guide/image.md).

## Networking

![arch network](https://4196336753-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LULg3WmBk4r0dWAdK9A%2Fuploads%2Fgit-blob-8bc8609a72cb2dc025f2ff25c4300f93f59c7b3e%2Farch-network.png?alt=media)

K8s network:

* Used for communication with the load balancer to allow each container to be accessible from a URL
* Implemented with Flannel

Tailscale network:

* Used for communication between cloud desktops and robots globally
* Managed with [Tailscale Dashboard](https://login.tailscale.com/admin/machines)

AWS Route53:

* Provides DNS records for redirecting traffic to the cluster


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://campus-rover.gitbook.io/lab-notebook/fiiva/vnc-cluster/operation-guide/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.