kubevious VS image-builder

Unlike the other tools mentioned in this post, Kubevious has no way of changing the cluster state. It is intended solely as an observability tool, focusing on potential issues in your cluster. It highlights potential threats and risks for every resource you may run.

kubevious: UI tool and query the cluster with regex https://github.com/kubevious/kubevious

In many ways, Kubevious is like many other Kubernetes Dashboard alternatives in that it provides the capability to view, edit, and maintain your configurations. However, Kubevious is going strong on one specific selling point: simplicity.

But since you asked I’ll give quick summary to the scope of the change. Prior version of Kubevious comes with a graphival view, where resources are reresented in a tree structure under namespaces and grouped in a logical group of “application”. This lets you see configmaps, services, ingresses, etc that are somehow related to this application. See here: https://github.com/kubevious/kubevious

You should also check https://github.com/kubevious/kubevious

I know when I started this article I mentioned install Kubevious into the cluster to unveil its full power. But if you just want to give it a try you can try using kubevious portable version that runs on your local machine but with limited functionality like e.g., time-machine is not there, etc.

Today we are going to see about Kubevious, this IDE, takes not so obvious approach, with features like analyzing your Kubernetes cluster like

True but here's what I use. https://github.com/kubernetes-sigs/image-builder

or build your own https://github.com/kubernetes-sigs/image-builder/tree/master/images/capi/packer/ova

https://github.com/kubernetes-sigs/image-builder

Is a tool that will allow the configuration of base images. It is actually a thin layer wrapper around packer and ansible