8000 Add ability to configure affinity and tolerations for scans and hooks by malexmave · Pull Request #804 · secureCodeBox/secureCodeBox · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@malexmave
Copy link
Member
@malexmave malexmave commented Nov 10, 2021

Description

This PR resolves #803 by adding affinity and tolerations to the ScanSpec and ScanCompletionHookSpec.

Currently in draft state. Tasks:

  • Add to ScanSpec and ScanCompletionHookSpec CRDs and re-generate them
  • Add to controller (pull information from CRD and put it into the pod)
  • Check if the JS definitions need to be updated (hooks, SDKs)
  • Add new inheritX labels
  • Add test cases for cascading hooks
  • Test everything
  • Double-check if the docs need to be updated anywhere or if everything is done automatically anyway
  • @J12934: Is this something that would be useful to also add to the values.yaml for the different scanners? That way, you could have specific scan types always run with a specific toleration / affinity and would not need to specify it every single time.

I will try to wrap this up later today so we can release it as part of 3.4 - that way the inconvenience of having to manually update CRDs can be lessened, as a CRD update is necessary anyway because of the new hook features. (Not looking forward to the merge conflicts - perhaps we should merge the other two PRs so I can quickly rebase on that branch to avoid that pain down the road?)

@malexmave malexmave added enhancement New feature or request CRD Improvements or additions to CRDs labels Nov 10, 2021
@malexmave malexmave added this to the v3.4.0 milestone Nov 10, 2021
@malexmave malexmave self-assigned this Nov 10, 2021
@malexmave malexmave changed the title Add ability to configure affinity and tolerations Add ability to configure affinity and tolerations for scans and hooks Nov 10, 2021
Signed-off-by: Max Maass <max.maass@iteratec.com>
Signed-off-by: Max Maass <max.maass@iteratec.com>
Signed-off-by: Max Maass <max.maass@iteratec.com>
Signed-off-by: Max Maass <max.maass@iteratec.com>
Signed-off-by: Max Maass <max.maass@iteratec.com>
Signed-off-by: Max Maass <max.maass@iteratec.com>
@malexmave malexmave force-pushed the feature/affinity-and-tolerations branch 2 times, most recently from 4a6f685 to 206517a Compare November 11, 2021 07:45
Signed-off-by: GitHub Actions <securecodebox@iteratec.com>
@malexmave
Copy link
Member Author

Okay, I broke something with my attempts to get this back on top of main, and even force-pushing this branch did not fix it. Since there isn't a lot of interesting history yet, I'll close this PR and open a new one that is less borked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CRD Improvements or additions to CRDs enhancement New feature or request
55B9

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use preemptible node for scans

2 participants

0