-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat/pdb: adding PDB to server and high priorityClass for jobs/plugins #100
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1ea5706
to
1233944
Compare
Hold until assigning jira card. |
/assign @jcpowermac @rvanderp3 |
|
@mtulio the check for the taint would need to change, would you do that in this pr or follow up? provider-certification-tool/pkg/run/run.go Line 237 in f27f508
|
Decopling pre-run functions for check and setup for `run` command. Implementing PDB in the pre-run setup to protect the sonobuoy server for disruptions. Setting priority classes for plugin/jobs. Making the dedicated node and taints optional using CLI flags.
@jcpowermac what about making dedicated (node selector) and taints optional being able to enable using flags? (please take a look at the latest version) |
This solutions seems not to be fully healthy yet. When running the new version (no taints, no selectors) I got the conformance test pod evicted, making the CLI stuck in the progress/running (another issue/improvement to check the pod):
|
The higher priority class for jobs managed by Sonobuoy seems not to be enough to keep the environment stable, in a regular deployment (w/o taints and node selector), we keep seeing (eventual) job pods eviction, and execution getting stuck in 3x3 deployment.
|
run
cleanup: Isolating pre runs for check and setupsTODO: