-
Notifications
You must be signed in to change notification settings - Fork 604
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
Reconcile ET properly with no reference #7423
Conversation
Signed-off-by: Calum Murray <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cali0707 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 |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #7423 +/- ##
==========================================
- Coverage 76.63% 75.55% -1.09%
==========================================
Files 259 261 +2
Lines 14270 14673 +403
==========================================
+ Hits 10936 11086 +150
- Misses 2778 3008 +230
- Partials 556 579 +23 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Calum Murray <[email protected]>
/hold Let's do this in ET_v1b3, not in this v1b2 version! See: #7304 |
// 1. Check if there is a reference | ||
// a) if not, reconcile to true | ||
// b) if yes, continue reconciling | ||
// 2. Verify the Reference exists. |
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.
I like having this comment here. thx
Signed-off-by: Calum Murray <[email protected]>
func NewEventType(name, namespace string, o ...EventTypeOption) *v1beta3.EventType { | ||
et := &v1beta3.EventType{ |
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.
I think this should land in new package testing/v1beta3
. Perhaps the package was supposed to be introduced by v1beta3
PR. :)
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.
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.
I'm happy to update this either in this PR or a separate PR if we want, but this file seemed to be using v1beta2
so I had assumed it would be fine to bump to v1beta3
:)
/retest-required |
/hold spec:
description: My ET no ref
reference:
apiVersion: eventing.knative.dev/v1
kind: Broker
name: default
namespace: default
source: /yo/man
type: blah.blub
status: {} I see this still uses the wrong defaulting /cc @dsimansk |
@matzew I think the problem is that the cluster still has the v1beta2 CRD, not the v1beta3 CRD. When I get the CRD from the cluster after building from main, I get v1beta2. |
The defaulting is just wrong, so perhaps we need to change that, we do need the CRD version. yes That's a new different PR. See the old issues for all of this, there are a plenty of PRs that are needed in order to fully get it. Here is a list of old issues (and they have links to PRs): We can also wait, and do all of that AFTER the 1.13 reelease - in order to relax things, and buy time |
@matzew: GitHub didn't allow me to request PR reviews from the following users: Cali0707. Note that only knative members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
Signed-off-by: Calum Murray <[email protected]>
The newest commit fixed the defaulting behaviour, but it uncovered the following issue:
As such, I think this should be on hold until after the v1beta3 CRD is present |
Signed-off-by: Calum Murray <[email protected]>
@Cali0707: The following tests failed, say
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. I understand the commands that are listed here. |
PR needs rebase. 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. |
@pierDipi it would work if we served a v1beta3 CRD. I could update it to work on v1beta2 if we want to change the reconcile behaviour for v1beta2 wrt no reference being an allowed state for the CRD. Otherwise, we could close this. WDYT? I'm a little confused about the current plan for event types tbh |
Thanks for raising that there is confusion, let's discuss this in the working group meeting after the release |
/close |
@matzew: 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. |
Fixes #7264
Feature track: https://docs.google.com/document/d/1US5Ve0CwhXwO8pUudN36vLkuSetEtSgwQ1btuG_9Xmk/edit
Proposed Changes
Pre-review Checklist
Release Note
Docs