Integration with KIND (Kubernetes in Docker)

[krzko]

Description

I would like to request the integration of run-o11y-run with Kind (Kubernetes in Docker). This feature would allow users to easily deploy their observability stack using Kubernetes manifests generated from the docker-compose.yml file used by run-o11y-run.

Currently, run-o11y-run provides a convenient way to run a local observability stack using Docker Compose. However, as many developers and teams are adopting Kubernetes for local development and testing, having the ability to deploy the stack as Kubernetes resources would be highly beneficial.

Proposed Solution

The proposed solution is to enhance run-o11y-run with a new command or flag that generates Kubernetes manifests from the existing docker-compose.yml file. These generated manifests can then be used to deploy the observability stack using Kind or any other Kubernetes cluster.

The integration could include the following steps:

• Parsing the docker-compose.yml file and extracting the relevant services, volumes, and network configurations.
• Converting the extracted configurations into Kubernetes manifest files (e.g., Deployment, Service, ConfigMap).
• Providing an option to output the generated manifests to a specified directory.
• Optionally, supporting the deployment of the generated manifests to a Kind cluster directly from run-o11y-run.

Expected Behaviour

After integrating run-o11y-run with Kind, users would be able to generate Kubernetes manifests from their existing docker-compose.yml file and deploy the observability stack to a local Kind cluster. This would provide a seamless transition for developers and teams who are already using Kind for local Kubernetes development.

Additional Context

Kind (Kubernetes in Docker) has gained popularity as a lightweight and fast option for running local Kubernetes clusters. Integrating run-o11y-run with Kind would align with industry trends and make it easier for users to adopt and leverage Kubernetes for their observability needs.