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
I am suggesting this as I am currently having experiencing a very flanky (faulty?) nginx ingress controller with kind when working on #698 . The request seems to hang from time to time. Even with tls disabled, the problem still persists.
By patching /etc/hosts with $(minikube ip) testing.cryostat, we no longer need to specify Host header or workaround to send API request directly to ingress controller service. I suppose this should be possible on Github runner :D
Describe the feature
Seems like we can use
minikube
in CI instead ofkind
. This should give us a more reliable cluster and easy way to test ingress hostname on k8s.Tutorial: https://minikube.sigs.k8s.io/docs/tutorials/setup_minikube_in_github_actions/
Github Action: https://github.com/medyagh/setup-minikube
Anything other information?
I am suggesting this as I am currently having experiencing a very flanky (faulty?) nginx ingress controller with kind when working on #698 . The request seems to hang from time to time. Even with tls disabled, the problem still persists.
A "compressed" log is shown below when inspecting ingress controller pod.
Moving to minikube seems to solve the issue.
The text was updated successfully, but these errors were encountered: