-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
base: main
Are you sure you want to change the base?
Add feature flag treat-pod-as-always-schedulable #15397
Conversation
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 Once the patch is verified, the new status will be reflected by the 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. |
e5cb758
to
7f8e56d
Compare
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 ... |
7f8e56d
to
b7433df
Compare
@SaschaSchwarze0 gentle ping. |
/ok-to-test |
b7433df
to
871e63a
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: SaschaSchwarze0 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 |
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. |
871e63a
to
a022e64
Compare
a022e64
to
7f7abc4
Compare
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]>
7f7abc4
to
5303dc0
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
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. |
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:
treat-pod-as-always-schedulable
is added with default Disabled.Release Note