-
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
Default the service links flag setting to false in knative #9622
Default the service links flag setting to false in knative #9622
Conversation
See knative#8498 for why are we doing this. Fixes knative#8563
Codecov Report
@@ Coverage Diff @@
## master #9622 +/- ##
=======================================
Coverage 88.16% 88.16%
=======================================
Files 176 176
Lines 8414 8416 +2
=======================================
+ Hits 7418 7420 +2
Misses 754 754
Partials 242 242
Continue to review full report at Codecov.
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor, vagababov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-serving-upgrade-tests:
|
/retest |
New changes are detected. LGTM label has been removed. |
It seems we were ignoring defaulting only in the revision itself, but completely failing to disable it when coming via config/service. |
/retest |
@@ -46,6 +41,11 @@ func (rts *RevisionTemplateSpec) SetDefaults(ctx context.Context) { | |||
|
|||
// SetDefaults implements apis.Defaultable | |||
func (rs *RevisionSpec) SetDefaults(ctx context.Context) { | |||
// SetDefaults may update revision spec which is immutable. | |||
// See: https://github.com/knative/serving/issues/8128 for details. | |||
if apis.IsInUpdate(ctx) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We had this in Revision because Revision is immutable. RevisionSpec is not immutable in all contexts.
Putting this here means that pre-existing resources won't have defaulting applied, which seems to me like it'll be breaking.
I'd like to understand what broke a bit better, and if another change is needed, then let's try and do that separately first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure.
BAsically here we did upgrade from nil
EnableServiceLinks to a real value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you have in mind that should be defaulted that wasn't before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that also those can be defaulted in reconciler itself.
Is the intent to migrate existing revisions? Let me know if I'm missing something but could we do either of the following:
|
So always resetting is a problem, since upgrade test is unhappy (can be fixed, but 🤷 )
|
/close |
@vagababov: Closed this PR. In response to this:
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/test-infra repository. |
See #8498 for why are we doing this.
Fixes #8563
/assign mattmoor