-
Notifications
You must be signed in to change notification settings - Fork 110
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
Validation jobs should run on the jobs node group #1148
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale Still relevant @maxgio92 ? |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/close We now have a single drivers config validate job that runs on the jobs node group: https://github.com/falcosecurity/test-infra/blob/master/config/jobs/build-drivers/validate-dbg.yaml |
@FedeDP: 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. |
Feature request
Validation jobs should run on the jobs node group.
They should be configured with appropriate selection and tolerations, at
PodSpec
-level. E.g.:Additional context
Otherwise, those jobs would run on the Prow-dedicated node group.
For examples, take a look at https://github.com/falcosecurity/test-infra/blob/master/config/jobs/build-drivers/.
The text was updated successfully, but these errors were encountered: