-
Notifications
You must be signed in to change notification settings - Fork 43
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
Regarding use-case of the tools #51
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
/lifecycle frozen |
@MichaelWasher: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hey @MichaelWasher, the repo together with the README is about to get updated with the new tools and rules for 4.12. If you have some specific use-case that needs to be automated with tools/scripts let's discuss it :) |
I have noted the
Gathering logs is not in the scope of these scripts and are better suited on the openshift/must-gather image
quote from the README and have questions about when to / when to not use this repo for tools.I can see that there are a number of scripts that perform tests on the current state of the network, similar to sanity checks or unit-tests on the network. I do not see tools that collect information for further debug, such as collecting PCAPs or running / collecting iPerf output.
Is this the appropriate place for writing these kinds of tools or is it intended for this repo to contain only smoke-tests and pass/fail tests on the network?
The text was updated successfully, but these errors were encountered: