Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Consider using minikube for CI #701

Closed
tthvo opened this issue Dec 21, 2023 · 3 comments
Closed

[Request] Consider using minikube for CI #701

tthvo opened this issue Dec 21, 2023 · 3 comments
Assignees
Labels
ci feat New feature or request question Further information is requested

Comments

@tthvo
Copy link
Member

tthvo commented Dec 21, 2023

Describe the feature

Seems like we can use minikube in CI instead of kind. 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.

$ curl -L -k -H 'HOST: testing.cryostat' https://ingress-nginx-controller.ingress-nginx.svc/health -v --trace-time
03:55:20.493697 * Host ingress-nginx-controller.ingress-nginx.svc:443 was resolved.
03:55:20.493773 * IPv6: (none)
03:55:20.493788 * IPv4: 10.96.74.150
03:55:20.493831 *   Trying 10.96.74.150:443...
03:55:20.494022 * Connected to ingress-nginx-controller.ingress-nginx.svc (10.96.74.150) port 443
03:55:20.497414 * ALPN: curl offers h2,http/1.1
03:55:20.497678 * TLSv1.3 (OUT), TLS handshake, Client hello (1):


A "compressed" log is shown below when inspecting ingress controller pod.

[alert] 29#29: sendmsg() failed (9: Bad file descriptor)
[alert] 29#29: fork() failed while spawning "worker process" (11: Resource temporarily unavailable)
[alert] 1258#1258: pthread_create() failed (11: Resource temporarily unavailable)
[alert] 28#28: worker process 1067 exited with fatal code 2 and cannot be respawned

Moving to minikube seems to solve the issue.

@tthvo tthvo added question Further information is requested feat New feature or request ci labels Dec 21, 2023
@tthvo
Copy link
Member Author

tthvo commented Dec 21, 2023

easy way to test ingress hostname on k8s.

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

@tthvo tthvo self-assigned this Dec 22, 2023
@tthvo tthvo closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2023
@ebaron
Copy link
Member

ebaron commented Dec 22, 2023

Thanks anyways for taking the initiative!

@tthvo
Copy link
Member Author

tthvo commented Dec 22, 2023

Ahha thanks! Tho, I kinda like how neatly minikube can be configured and the variety of cluster configs it offers...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci feat New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants