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

feat: configure scheduler on controller-manager and audit pods #3560

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

gergelysotidm
Copy link

What this PR does / why we need it:
Enables the configuration of a non-default k8s scheduler on both the audit and controller-manager pods.

Relevant for people who run an alternate scheduler next to the default one. Especially relevant on AWS/EKS, because there the users are not allowed to configure the scheduler.

The default value will use the default k8s scheduler (if you leave the setting out, k8s will assign the pods to the default-scheduler).

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #

Special notes for your reviewer:

@gergelysotidm gergelysotidm requested a review from a team as a code owner September 24, 2024 09:38
@codecov-commenter
Copy link

codecov-commenter commented Sep 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.71%. Comparing base (3350319) to head (2592fdc).
Report is 164 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (3350319) and HEAD (2592fdc). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (3350319) HEAD (2592fdc)
unittests 2 1
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3560      +/-   ##
==========================================
- Coverage   54.49%   47.71%   -6.79%     
==========================================
  Files         134      221      +87     
  Lines       12329    18699    +6370     
==========================================
+ Hits         6719     8922    +2203     
- Misses       5116     8935    +3819     
- Partials      494      842     +348     
Flag Coverage Δ
unittests 47.71% <ø> (-6.79%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

| externalCertInjection.enabled | Enable the injection of an external certificate. This disables automatic certificate generation and rotation | `false` |
| externalCertInjection.secretName | Name of secret for injected certificate | `gatekeeper-webhook-server-cert` |
| externaldataProviderResponseCacheTTL | TTL for the external data provider response cache. Specify the duration in 'h', 'm', or 's' for hours, minutes, or seconds respectively. | `3m` |
| schedulerName | Name of the kubernetes scheduler to be used for the audit and controller pods. | `3m` |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| schedulerName | Name of the kubernetes scheduler to be used for the audit and controller pods. | `3m` |
| schedulerName | Name of the kubernetes scheduler to be used for the audit and controller pods. | `default-scheduler` |

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops, fixed :)

@JaydipGabani
Copy link
Contributor

@gergelysotidm you need to sign your commit for DCO check to pass ☺️ .

@gergelysotidm gergelysotidm force-pushed the feat/non_default_scheduler branch 3 times, most recently from b82c877 to 8558fb7 Compare October 21, 2024 18:54
@JaydipGabani
Copy link
Contributor

@gergelysotidm pls resolve the conflicts ☺️

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

Successfully merging this pull request may close these issues.

3 participants