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
GH actions - E2E tests for namespaced broker #2450
GH actions - E2E tests for namespaced broker #2450
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aliok 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 Report
@@ Coverage Diff @@
## main #2450 +/- ##
============================================
+ Coverage 64.59% 64.64% +0.05%
- Complexity 708 709 +1
============================================
Files 146 146
Lines 9803 9803
Branches 223 223
============================================
+ Hits 6332 6337 +5
+ Misses 3042 3035 -7
- Partials 429 431 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
61f0698
to
3969bfd
Compare
a01ab14
to
bf20b7c
Compare
5bb12e6
to
3ba227e
Compare
1539916
to
048218f
Compare
/retest |
/test upgrade-tests_eventing-kafka-broker_main |
048218f
to
49e80b6
Compare
# TODO: going to be reverted once we have the Prow changes in https://github.com/knative/test-infra | ||
export BROKER_CLASS="Kafka" |
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.
Still hardcoded in Prow jobs. Gonna pass this once knative/test-infra#3466 is merged.
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.
# TODO: going to be reverted once we have the Prow changes in https://github.com/knative/test-infra | |
export BROKER_CLASS="Kafka" | |
# TODO: going to be reverted once we have the Prow changes in https://github.com/knative/test-infra | |
export BROKER_CLASS=${BROKER_CLASS:-"Kafka"} |
what about this option? that would facilitate running them locally without specifying the class since it would default to the existing/stable one.
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 personally always prefer explicit errors over invisible defaulting.
However, I am ok with that if you feel strong about it
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.
The job is there, can we fix the TODO
s?
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.
TODO: going to be reverted once we have the Prow changes in https://github.com/knative/test-infra
This is a bad comment of mine, sorry.
I want to make sure that I am not breaking any E2E tests for the regular KafkaBroker with this PR.
Similarly, in #2459, I am testing if E2E tests are passing for the namespaced broker.
So, I will remove that TODO in a separate PR when I am 100% sure that E2E tests are passing in both class.
/test upgrade-tests_eventing-kafka-broker_main |
7 similar comments
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main |
/test upgrade-tests_eventing-kafka-broker_main Trying agin... |
/test upgrade-tests_eventing-kafka-broker_main Trying head with #2469 |
This seems to be the issue: #2427 |
I am gonna try 2-3 more times and then disable the upgrade tests. |
// Namespaced broker controller | ||
injection.NamedControllerConstructor{ | ||
Name: "broker-namespaced-controller", | ||
ControllerConstructor: func(ctx context.Context, watcher configmap.Watcher) *controller.Impl { | ||
return broker.NewNamespacedController(ctx, watcher, brokerEnv) | ||
}, | ||
}, | ||
|
||
// Namespaced trigger controller | ||
injection.NamedControllerConstructor{ | ||
Name: "trigger-namespaced-controller", | ||
ControllerConstructor: func(ctx context.Context, watcher configmap.Watcher) *controller.Impl { | ||
return trigger.NewNamespacedController(ctx, watcher, brokerEnv) | ||
}, | ||
}, |
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're enabling these controllers which means that they will be released but I think we should solve the known issues first like:
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.
/hold
OK we need to make a decision:
- Release with poor CM support
- Block the release until CM issues are completely fixed
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'd prefer solving known issues because right now these deployments aren't debuggable at all, no tracing, no logging config or stale ConfigMaps contain buggy behavior (consumer and producer configs)
No, please going back at debugging is worst, someone needs to take a closer look at what's happening and de-flake jobs. |
I didn't understand. I don't want to fix an irrelevant issue part of this work. |
@aliok: 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. |
@aliok: 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. |
/close @pierDipi FYI, contents of this PR is in upstream/main already. |
@aliok: 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 #
Proposed Changes
Kafka
in Prow e2e testsRelease Note
Docs