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

speed up test runs #111

Open
mattfenwick opened this issue Apr 18, 2021 · 1 comment
Open

speed up test runs #111

mattfenwick opened this issue Apr 18, 2021 · 1 comment

Comments

@mattfenwick
Copy link
Owner

mattfenwick commented Apr 18, 2021

client-side:

server-side:

ideas:

  • reduce number of kubectl exec calls
  • avoid spinning up an agnhost binary for each network call
@lwr20
Copy link

lwr20 commented Jun 29, 2021

A couple more possible ideas (though note I've not read the code in this area, so bear that in mind):

  • run checks in parallel
  • run all the checks continuously within the pod and report current result via an http server (or equivalently a prom metrics endpoint) - so checking the overall connectivity map becomes a single curl to each pod
  • run a pod for each check that continuously does the check and report success/failure via its Readiness check? Then checking the overall connectivity map is simply a kubectl get po -A (or equivalent api call)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants