Connext.

Cyclone DDS.

FastDDS.

Gurum DDS.

ROS 2 Foxy Fitzroy.

ROS 2 Galactic Geochelone.

ROS 2 Humble Hawksbill.

ROS Melodic Morenia.

ROS Noetic Ninjemys.

AddToScheme adds the types in this group-version to the given scheme.

GroupVersion is group version used to register these objects.

SchemeBuilder is used to add go types to the GroupVersionKind scheme.

SchemeGroupVersion is group version used to register these objects.

BuildManager is the Schema for the buildmanagers API.

BuildManagerList contains a list of BuildManager.

BuildManagerSpec defines the desired state of BuildManager.

BuildManagerStatus defines the observed state of BuildManager.

DiscoveryServer is a custom resource that connects Robots and Fleets both locally and geoghraphically in DDS (UDP multicast) level.

DiscoveryServerList contains a list of DiscoveryServer.

DiscoveryServerSpec defines the desired state of DiscoveryServer.

DiscoveryServerStatus defines the observed state of DiscoveryServer.

Current usage of GPU cores belongs to a GPU instance (eg.

Launch description of a repository.

LaunchManager is the Schema for the launchmanagers API.

LaunchManagerList contains a list of LaunchManager.

LaunchManagerSpec defines the desired state of LaunchManager.

LaunchManagerStatus defines the observed state of LaunchManager.

MetricsExporter collects metrics from host machine and expose them from the Kubernetes API.

MetricsExporterList contains a list of MetricsExporter.

MetricsExporterSpec defines the desired state of MetricsExporter.

MetricsExporterStatus defines the observed state of MetricsExporter.

Notebook is the Schema for the notebooks API.

NotebookList contains a list of Notebook.

NotebookSpec defines the desired state of Notebook.

NotebookStatus defines the observed state of Notebook.

Generic status for any owned resource.

RelayServer is the Schema for the relayservers API.

RelayServerList contains a list of RelayServer.

RelayServerSpec defines the desired state of RelayServer.

RelayServerStatus defines the observed state of RelayServer.

Repository description.

VDI resource limits.

Robot is the custom resource that contains ROS 2 components (Workloads, Cloud VDI, Cloud IDE, ROS Bridge, Configurational Resources), robolaunch Robot instances can be decomposed and distributed to both cloud instances and physical instances using federation.

RobotArtifact is a non-functional resource that holds Robot's specifications.

RobotArtifactList contains a list of RobotArtifact.

RobotDevSuite is a custom resource that creates dynamically configured development environments for robots.

RobotDevSuiteList contains a list of RobotDevSuite.

RobotDevSuiteSpec defines the desired state of RobotDevSuite.

RobotDevSuiteStatus defines the observed state of RobotDevSuite.

RobotIDE creates and manages Cloud IDE resources and workloads.

RobotIDEList contains a list of RobotIDE.

RobotIDESpec defines the desired state of RobotIDE.

RobotIDEStatus defines the observed state of RobotIDE.

RobotList contains a list of Robot.

RobotSpec defines the desired state of Robot.

RobotStatus defines the observed state of Robot.

RobotVDI creates and manages Cloud VDI resources and workloads.

RobotVDIList contains a list of RobotVDI.

RobotVDISpec defines the desired state of RobotVDI.

RobotVDIStatus defines the observed state of RobotVDI.

ROSBridge is a custom resource that provisions ROS/2 bridge resources and workloads.

ROSBridgeList contains a list of ROSBridge.

ROSBridgeSpec defines the desired state of ROSBridge.

ROSBridgeStatus defines the observed state of ROSBridge.

Step is a command or script to execute when building a robot.

Robot's resource limitations.

Storage class configuration for a volume type.

Workspace description.

WorkspaceManager configures the ROS 2 workspaces and repositories by executing Kubernetes jobs.

WorkspaceManagerList contains a list of WorkspaceManager.

WorkspaceManagerSpec defines the desired state of WorkspaceManager.

WorkspaceManagerStatus defines the observed state of WorkspaceManager.

Instance type can be either `Server` or `Client`.

RMW implementation chooses DDS vendor for ROS 2.

ROS 2 distribution selection.