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

Add feature flag treat-pod-as-always-schedulable #15397

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SaschaSchwarze0
Copy link
Contributor

The feature flag allows to declare that Pods in the system will eventually all get scheduled and Revisions should therefore not be marked unschedulable

Fixes #14862

Proposed Changes

Unfortunately, I never got feedback in above issue, so trying with a PR now:

  • New feature treat-pod-as-always-schedulable is added with default Disabled.
  • If enabled, the revision reconciler will skip the check whether a pod is not scheduled and therefore never mark a revision as unschedulable.

Release Note

You can now set the new feature `treat-pod-as-always-schedulable` to enabled in the config-defaults ConfigMap. As a result, Knative will not mark revisions as Unschedulable when a Pod is not scheduled. This makes sense if you want to omit this transient state in clusters that have cluster-autoscaling set up, and you can guarantee that all Pods will be eventually scheduled.

@knative-prow knative-prow bot requested review from dprotaso and izabelacg July 19, 2024 12:30
@knative-prow knative-prow bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 19, 2024
Copy link

knative-prow bot commented Jul 19, 2024

Hi @SaschaSchwarze0. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-treat-pod-as-always-schedulable branch from e5cb758 to 7f8e56d Compare July 19, 2024 13:11
@SaschaSchwarze0
Copy link
Contributor Author

SaschaSchwarze0 commented Jul 19, 2024

Hm, I debugged the failing unit test and can see that when the code checks the config, that there is some config in the context with the right value but somehow what it gets has it empty. Need to check ...

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 3, 2024
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-treat-pod-as-always-schedulable branch from 7f8e56d to b7433df Compare October 17, 2024 11:49
@knative-prow-robot knative-prow-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 17, 2024
@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 7, 2025
@dprotaso dprotaso added this to the v1.18 milestone Jan 14, 2025
@skonto
Copy link
Contributor

skonto commented Jan 14, 2025

@SaschaSchwarze0 gentle ping.

@skonto
Copy link
Contributor

skonto commented Jan 14, 2025

/ok-to-test

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 14, 2025
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-treat-pod-as-always-schedulable branch from b7433df to 871e63a Compare January 14, 2025 12:35
Copy link

knative-prow bot commented Jan 14, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: SaschaSchwarze0
Once this PR has been reviewed and has the lgtm label, please assign dprotaso for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 14, 2025
@SaschaSchwarze0
Copy link
Contributor Author

SaschaSchwarze0 commented Jan 14, 2025

@SaschaSchwarze0 gentle ping.

Rebased, but I still do not understand the unit test case failure in pkg/reconciler/revision/table_test.go. In particular, the custom context with the custom feature flag does not work = the code does not get the expected feature flag status and I do not understand why.

EDIT1: I think I now understand it. table_test.go does the following which overwrites all config customizations done on the Ctx of the row.

		return revisionreconciler.NewReconciler(ctx, logging.FromContext(ctx), servingclient.Get(ctx),
			listers.GetRevisionLister(), controller.GetEventRecorder(ctx), r,
			controller.Options{
				ConfigStore: &testConfigStore{
					config: reconcilerTestConfig(),
				},
			})

EDIT2: Though, I do not understand why it works for other unit tests then (like the one that sets PodSpecInitContainers to Enabled).

EDIT3: Maybe because only the controller uses the configstore from its options.

EDIT4: Fixed.

@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-treat-pod-as-always-schedulable branch from 871e63a to a022e64 Compare January 14, 2025 13:57
@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 14, 2025
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-treat-pod-as-always-schedulable branch from a022e64 to 7f7abc4 Compare January 14, 2025 15:25
The feature flag allows to declare that Pods in the system will eventually all get scheduled and Revisions should therefore not be marked unschedulable

Signed-off-by: Sascha Schwarze <[email protected]>
@SaschaSchwarze0 SaschaSchwarze0 force-pushed the sascha-treat-pod-as-always-schedulable branch from 7f7abc4 to 5303dc0 Compare January 14, 2025 15:29
@knative-prow-robot knative-prow-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 14, 2025
Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.84%. Comparing base (19b9a09) to head (5303dc0).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15397      +/-   ##
==========================================
+ Coverage   80.78%   80.84%   +0.06%     
==========================================
  Files         222      222              
  Lines       18025    18029       +4     
==========================================
+ Hits        14561    14576      +15     
+ Misses       3092     3084       -8     
+ Partials      372      369       -3     

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Provide configuration option for revisions becoming Unschedulable
4 participants