Skip to content

Latest commit

 

History

History
71 lines (44 loc) · 4.32 KB

README.md

File metadata and controls

71 lines (44 loc) · 4.32 KB
Raw

Kubenet logo

Discord

Kubenet

The Kubenet community has been created with the goal to help network engineers understand the potential of kubernetes for network automation. While we discuss networking, we are not talking about CNI(s) here, but about using kubernetes as an automation engine to manage physical, virtual or containerized NOS(s).

The environment is build such that can leverage multiple vendors. We use srlinux for now as this is open to use, but we would welcome other vendors contributions.

If you are interested to learn and discuss join us

This repository contains the source for learn.kubenet.dev.

Why

Kubernetes stands out as the most extensive and robust automation and orchestration system available today, already leveraged across many industries. The question to ask here is why is the networking industry not leveraging kubernetes for network automation. This community is setup to help understand the potential of kubernetes for network automation.

Here are some attributes to consider why kubernetes is a good automation platform:

  • Open Source: As an open-source platform, Kubernetes offers transparency, flexibility, and a collaborative community-driven approach. This fosters innovation and continuous improvement.
  • Highly Extendable: Kubernetes is designed to be highly extendable, allowing for customization and integration with various tools and services to meet specific needs.
  • Vast Ecosystem: The Kubernetes ecosystem is immense, with a wide range of tools, plugins, and extensions available. This ecosystem provides the resources needed to build comprehensive automation solutions.
  • Declarative Model: Kubernetes uses a declarative model, making it easier to define and manage the desired state of network configurations.
  • Event-Driven and Continuous Reconciliation: Kubernetes supports event-driven automation and continuous reconciliation, ensuring that the network’s state is consistently aligned with the defined configurations.
  • Collaborative Approach with GitOps: Leveraging GitOps principles, Kubernetes enables a collaborative approach to network management. Changes can be tracked, reviewed, and deployed using version control systems, enhancing transparency and collaboration.
  • Extensive Knowledge Base: The widespread adoption of Kubernetes means there is a vast knowledge base and a large community of experts. This allows organizations to leverage existing expertise to extend and optimize their automation systems.

Use cases

Independent on physical, virtual or containerized networking systems

Use cases:

  • Datacenter networking
  • WAN networking
  • Peering
  • Access/Campus networking
  • Core networking
  • Backhaul/Fronthaul
  • Cloud Networking

Scenario's:

  • day-0, day-1, day-2 operations
  • lifecycle management
  • config management

Join us

Join us on this journey as we learn how to leverage kubernetes for network automation.

Have questions, ideas, bug reports or just want to chat? Come join our discord server.

License and governance

Code in the Kubenet repositories licensed with Apache License 2.0. At the moment the project is governed by the benevolent dictatorship of @henderiw @steiler @karimra and @hansthienpondt . On the long run we plan to move to a meritocracy based governance model.

Contribute to the documentation

How to compile?

We are using containers to build the documentation, therefore you need to have Docker or Podman installed.

You can simply issue make in the root folder. This will compile the documentation and expose the documentation in https://localhost:8000 if you would like to use a different port, just override the PORT variable. For example using port 1313 is with make PORT=1313 .