Replies: 1 comment
-
I think it's not a good fit for Netbox. Kubernetes pods are generally dynamic: they can be moved between hosts, they can be replicated horizontally etc. Netbox is intended as a source-of-truth: you push data from Netbox to other systems, you don't use it as a portal on data collected from other systems. If you want to see where your containers are running, then use a front-end built for that (e.g. portainer, rancher, openshift) If you wanted to use Netbox as a SOT for Kubernetes, such that adding something in Netbox causes it to be created in Kubernetes, then you'd be creating Kubernetes resource definitions from Netbox: so you'd want to model Deployments, StatefulSets, PVCs etc. I guess that could be done with its own data models in a plugin. But I can't think of anyone who'd want to do this, rather than taking an Infrastructure-As-Code approach. |
Beta Was this translation helpful? Give feedback.
-
There is support for VM modeling in Netbox, and maybe stuff in Kubernetes can be modeled via making containers look like VMs. But, is there a better way?
Beta Was this translation helpful? Give feedback.
All reactions