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
RIght now there is no CI that runs with each PR. We should have a setup where each PR triggers a test run.
We have it, it runs the tests on GKE through circle ci. But this would need contributors to set up their own GKE instance to have their PR tested, which can be a PITA.
So maybe something based on minikube on some other CI (or maybe even the same) wouldn't be a bad idea, especially if that would allow us to run the tests locally.
I haven't had a look at how it is being done currently, though, so I don't know the details.
@surajssd Here is the commit showing the changes we made to migrate the tests from running on Minikube to running successfully on GKE. Notice we had to change the bind-config service type from NodePort to LoadBalancerhere.
RIght now there is no CI that runs with each PR. We should have a setup where each PR triggers a test run.
Proposal:
We can have a single node k8s setup on Semaphore CI, which runs as following:
minikube
withvm-driver none
.kubeadm
to start the master and then allow it to schedule pods.The text was updated successfully, but these errors were encountered: