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

Broker, Trigger, and Namespace Controllers #788

Merged
merged 191 commits into from
Mar 18, 2019

Conversation

Harwayne
Copy link
Contributor

@Harwayne Harwayne commented Feb 7, 2019

Proposed Changes

  • Initial implementations of the Broker and Trigger controllers.
  • Initial implementation of the eventing Namespace watcher.

With thanks to:

  • @nachocano - Who authored large swathes of the PR.
  • @grantr - Who also authored parts of the PR.
  • @vaikas-google and @n3wscott - For testing the intermediate states of the PR.

Release Note

Need to apply the two new types (Broker and Trigger) or the eventing controller will not start.

@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 7, 2019
@googlebot googlebot added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Mar 14, 2019
@nachocano
Copy link
Contributor

Created knative/eventing-contrib#252 in eventing-sources to add broker read only permissions. It should be merged right after this one, otherwise sources won't be able to point to brokers.

@vaikas
Copy link
Contributor

vaikas commented Mar 15, 2019

/approve

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vaikas-google

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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 15, 2019
@n3wscott
Copy link
Contributor

I got this to work after not reading the documentation and not creating the correct service account and role binding.

There is a bug in this code, the broker becomes ready when it does not have pods for the filter. The ingress pods come up and the filter pods never did.

I updated my chatbot demo to broker/trigger, here are the changes:

botless/slack#1
botless/commands#1
botless/parser#1

@Harwayne
Copy link
Contributor Author

There is a bug in this code, the broker becomes ready when it does not have pods for the filter. The ingress pods come up and the filter pods never did.

I agree, #915.

Mark the Broker's Ingress and Filter status condidionts failed when they have failed.
Do not DeepCopy() in Reconcile(), as controller-runtime already did it for us
@knative-metrics-robot
Copy link

The following is the coverage report on pkg/.
Say /test pull-knative-eventing-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/eventing/v1alpha1/broker_defaults.go Do not exist 100.0%
pkg/apis/eventing/v1alpha1/broker_types.go Do not exist 76.9%
pkg/apis/eventing/v1alpha1/broker_validation.go Do not exist 100.0%
pkg/apis/eventing/v1alpha1/trigger_defaults.go Do not exist 100.0%
pkg/apis/eventing/v1alpha1/trigger_types.go Do not exist 77.8%
pkg/apis/eventing/v1alpha1/trigger_validation.go Do not exist 100.0%

@n3wscott
Copy link
Contributor

/lgtm

💪

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 18, 2019
@knative-prow-robot knative-prow-robot merged commit 76603c8 into knative:master Mar 18, 2019
@Harwayne Harwayne deleted the broker-new-model branch May 9, 2019 18:58
matzew added a commit to matzew/eventing that referenced this pull request Sep 3, 2020
Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.