Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

A network cloud you can take anywhere, backed by open source.

NotificationsYou must be signed in to change notification settings

datum-cloud/datum

Repository files navigation

Datum is a network cloud you can take anywhere, backed by open source.

The Datum control plane is a collection of multiple projects developed withKubernetes control plane technology, most of which can be installed into nativeKubernetes clusters.

Get started

Documentation

Our documentation is available atdocs.datum.net. Ifyou want to learn more about what's under development or suggest features,please visit ourfeedback site.

Key Components

API Server

The Datum API server leverages Kubernetes API server libraries to enablecompatibility with existing Kubernetes ecosystems tooling such as kubectl, helm,kustomize, Terraform, Pulumi, Ansible, kubebuilder, operator-sdk, and more.

While the Datum API server exposes a handful of existing Kubernetes API typessuch as Secrets and ConfigMaps, you will not find definitions for Pods,Deployments, Services, etc. This approach takes advantage of recent developmentsin the Kubernetes project to build ageneric control plane, exposinglibraries that external software can depend on and build upon.

Kubernetes Operators

Datum leverages theoperator pattern to define APIs and implementcontrollers via the use ofkubebuilder. Each Datum operator canbe deployed into any native Kubernetes cluster that meets minimum API versionrequirements, and does not rely on specific functionality provided by the DatumAPI server.

APIs:

  • Networks, NetworkContexts, NetworkBindings, and NetworkPolicies
  • SubnetClaims and Subnets
  • IP Address Management (IPAM)

Controller responsibilities:

  • Creating NetworkContexts as required by NetworkBindings.
  • Allocating Subnets to SubnetClaims

APIs:

  • Workloads, WorkloadDeployments, and Instances

Controller responsibilities:

  • Creating one or more WorkloadDeployments for candidate locations based onWorkload placement intent.
  • Scheduling WorkloadDeployments onto Locations.

TheWorkloads RFC is recommended reading for those interested inthe design goals of this system.

Integrates with the Network Services and Workload Operators to provisionresources within Google Cloud Platform (GCP). This operator connects to:

  • An upstream control plane hosting Datum entities
  • An infrastructure control plane runningGCP ConfigConnector

Controller responsibilities:

  • Maintaining instances as Virtual Machines in GCP.
  • Maintaining VPC related entities such as networks and subnets.
  • Discovering instances provisioned by GCP controllers, such as managed instancegroups.

Get involved

If you choose to contribute to any of our projects, we would love to work with you to ensure a great experience.


[8]ページ先頭

©2009-2025 Movatter.jp