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
My team works on a few microservices.
Those services are deployed (together with other supporting services) to Kubernetes via a Helm chart.
Currently, we use minikube to test the helm chart and run end-to-end tests.
However, the minikube is started and the chart is deployed before the e2e test build is started.
I thought that it would great to have a JUnit "minikube" rule, similar to, e.g., DockerComposeContainer.
I was wondering if "minikube" module is something that the maintainers see fit for this project?
If yes - I'm open to contributing to this module.
The text was updated successfully, but these errors were encountered:
I realise that this is a very old ticket, but we may have a solution to some users' needs in the works.
#4485 / #4582 is for a K3S module, aimed at making it easy to test things that have a direct need to communicate with a Kubernetes API. I would not envisage this being a good tool to use for deploying many services to, but for some use cases (like testing k8s operators) containerised k3s can work well.
My team works on a few microservices.
Those services are deployed (together with other supporting services) to Kubernetes via a Helm chart.
Currently, we use minikube to test the helm chart and run end-to-end tests.
However, the minikube is started and the chart is deployed before the e2e test build is started.
I thought that it would great to have a JUnit "minikube" rule, similar to, e.g.,
DockerComposeContainer
.I was wondering if "minikube" module is something that the maintainers see fit for this project?
If yes - I'm open to contributing to this module.
The text was updated successfully, but these errors were encountered: