Integrate Kubernetes Tool with Dashboard

[rstuhlmuller]

Hey Homarr community! I'd like to propose an idea to integrate Kubernetes into our dashboard. As many of us are using Kubernetes to manage our containerized applications, it would be incredibly useful to have a dedicated dashboard item to monitor our clusters.

Motivation:
Currently, I'm using multiple tools to monitor my Kubernetes cluster, which can be overwhelming and time-consuming. Having a unified view of my cluster's performance, node status, and pod health would greatly simplify my workflow. I believe this integration would be a valuable addition to Homarr, making it an even more comprehensive monitoring solution.

Proposed Implementation:
To integrate Kubernetes into Homarr, I suggest the following:

1. Kubernetes API Connection: Create a new connection type in Homarr to connect to a Kubernetes cluster using the Kubernetes API. This would allow users to input their cluster's API endpoint, credentials, and namespace.
2. Dashboard Item: Design a new dashboard item specifically for Kubernetes, which would display key metrics such as:
   • Node status (e.g., running, pending, failed)
   • Pod health (e.g., running, pending, failed)
   • Deployment status (e.g., rolling updates, failed deployments)
   • Resource usage (e.g., CPU, memory, storage)
3. Widgets: Offer various widgets to display the above metrics, such as:
   • Node and pod grids
   • Deployment status charts
   • Resource usage gauges
4. Alerting: Integrate Kubernetes events and alerts into Homarr's existing alerting system, allowing users to set up custom notifications for specific events (e.g., node failures, deployment errors)

Benefits:
The integration of Kubernetes into Homarr would provide several benefits, including:

• Unified Monitoring: A single dashboard for monitoring all aspects of our infrastructure, including Kubernetes clusters.
• Simplified Troubleshooting: Easy identification of issues and errors within the cluster, reducing downtime and improving overall system reliability.
• Enhanced Visibility: Real-time insights into cluster performance, enabling proactive optimization and resource planning.

Next Steps:
If this idea gains traction, I'd be happy to help with the implementation. I propose the following steps:

1. Discussion: Continue discussing this idea to gather feedback, suggestions, and requirements from the community.
2. Design: Create wireframes and mockups of the proposed dashboard item and widgets.
3. Development: Implement the integration, starting with the connection type and dashboard item, followed by the widgets and alerting features.

What do you think, Homarr community? Is this something you'd like to see in a future release? Do you have any suggestions or ideas to share? Let's discuss!

[manuel-rw]

@oben01 what do you think? Can you look into this?
@rstuhlmuller are you willing to contribute? This is a big change you are requesting and we do not have the capacity to implement every small feature in Homarr.

As a sidenote, we will not implement #4, since Homarr is not an alerting tool and we don't want to make it such.
Please use alternatives that have been built up from the ground for that purpose.

[oben01]

First of all, apologies for the delayed response!

We actually already have a Kubernetes dashboard integration available. have you had a chance to try it out yet? You can find the documentation here: https://homarr.dev/docs/integrations/kubernetes. This is our first iteration of the integration, and we definitely see room for improvement and new features.

At the moment, widgets for Kubernetes are not yet developed. We’d really appreciate any help, whether it's feedback or direct contributions to push this forward. If you're interested in contributing, we’ve prepared a development guide here: https://homarr.dev/docs/advanced/development/kubernetes/.

Regarding point #4 (alerting), we currently don’t plan to implement a built-in alerting system in Homarr, as it’s outside the scope of the project. Homarr is not intended to be an alerting tool. However, in the future, if we open up support for external community driven extensions, this might become a possibility.

Thanks again for your interest and suggestions looking forward to your thoughts and any contributions!