Skip to content

Release v0.91

Pre-release
Pre-release
Compare
Choose a tag to compare
@vinaykul vinaykul released this 13 Mar 12:38
· 8 commits to dev-next since this release
v0.91
699c593
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This release brings integration of Mizar pod networking solution with Arktos project (A fork of Kubernetes project that adds capabilities for true multi-tenancy orchestration of pods and virtual machines). There is no existing pod networking solution that supports mult-tenancy networking. This release of Mizar project fills the gap.

Arktos scale out architecture allows for deployment of multiple cluster-master instances (called tenant partitions) where each master instance has its own set of etcd, apiserver, scheduler, and controllers (except node controller). Each tenant partition can support multiple tenant users. And each tenant partition master has a global view worker nodes across multiple resource partitions where each resource partition is its own cluster with a master that runs etcd, apiserver, and node controller designed to focus mainly on worker node resource management in that cluster. In this way, Arktos scale out deployments allow for scaling the number of nodes available for pod deployment beyond known limits in Kubernetes.

The following key features were implemented to facilitate the integration:

  1. Support Mizar multi-tenancy networking deployment for the following Arktos deployment modes:
    • Scale out architecture (multiple tenant partitions and multiple resource partitions with multiple tenant-users).
    • Scale up architecture (single cluster deployment with multiple tenant-users)
    • Local cluster deployment with multiple tenant-users
    • Mizar networking support for both pods and virtual machines with with full network isolation for multiple tenant users.
  2. Implement gRPC server mode in Mizar node agent (transitd daemonset) to enable multiple Mizar operators from two or more tenant partitions program eBPF maps in any given worker node that is shared across multiple tenant clusters.
  3. Implement gRPC server mode of operation in Mizar operator that enables Mizar network controller in each tenant partition invoke Mizar APIs for multiple tenant users.
  4. Support the creation of multiple VPC objects where each VPC represents a single tenant user which has full network isolation from other tenant users.
  5. Co-locate Mizar operator with tenant apiserver for simplicity, performance, and efficiency.
Assets 4
Loading