You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hi there! I recently developed a Kubernetes operator that automatically generates a Homer configuration by reading annotations from Kubernetes Ingress and Traefik IngressRoute resources. This solution eliminates the need for manual configuration and decentralizes the process of creating dashboards.
The project is full CI/CD and has a Helm chart and Docker image. Furthermore, it makes no alternations to the existing Homer image as the operator runs as an optional side-car container.
Describe the solution you'd like
I’d like to propose adopting this operator as part of the main Homer project. It could serve as an official solution for Kubernetes users, providing a robust and automated way to manage Homer configurations. The operator part is also optional. It can be disabled by the user.
Describe alternatives you've considered
If adopting the operator into the main project isn’t feasible, I’d like to request adding it to the Kubernetes documentation page here: https://github.com/bastienwirtz/homer/blob/main/docs/kubernetes.md. This would help Kubernetes users discover and benefit from the operator.
Additional context
I started the project because none of the existing solutions had the flexibility I needed and most weren't packaged as a Helm chart with automatic updates and full CD.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi there! I recently developed a Kubernetes operator that automatically generates a Homer configuration by reading annotations from Kubernetes Ingress and Traefik IngressRoute resources. This solution eliminates the need for manual configuration and decentralizes the process of creating dashboards.
The project is hosted at https://github.com/arch-anes/homer-operator and here's an example dashboard completely generated from annotations: https://dash.belfodil.ca/
The project is full CI/CD and has a Helm chart and Docker image. Furthermore, it makes no alternations to the existing Homer image as the operator runs as an optional side-car container.
Describe the solution you'd like
I’d like to propose adopting this operator as part of the main Homer project. It could serve as an official solution for Kubernetes users, providing a robust and automated way to manage Homer configurations. The operator part is also optional. It can be disabled by the user.
Describe alternatives you've considered
If adopting the operator into the main project isn’t feasible, I’d like to request adding it to the Kubernetes documentation page here: https://github.com/bastienwirtz/homer/blob/main/docs/kubernetes.md. This would help Kubernetes users discover and benefit from the operator.
Additional context
I started the project because none of the existing solutions had the flexibility I needed and most weren't packaged as a Helm chart with automatic updates and full CD.
The text was updated successfully, but these errors were encountered: