Kubernetes Custom Resources (CRD)

Netris operated on-prem clouds can be provisioned and managed using Kubernetes Custom Resources (CRD). Parts or even the entire network environment can be managed by CI/CD pipeline of Kubernetes YAML files, simplifying deployment and ongoing changes of your data center and edge networks.

What’s the key conceptual difference of Kubernetes operator between Netris vs. legacy network vendors?

With legacy systems, you will need to describe specific details for every network device and ensure there are no conflicting configurations across historically crafted configs throughout the entire network. (pets approach)

With Netris, you only need to declare high-level services for the Netris controller, and Netris takes care of all the configurations automatically. (cattle approach)

The Netris-Operator on Github: Netris-Operator

Watch this Demo video

See an example of IaC (Infrastructure as Code) using Kubernetes Custom Resources.

Learn more