You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changes in #11404 showed that local running of the eventing controller doesn't work anymore. Beside setting environment variables the controller had to react at runtime.
Expected result
When the eventing-controller runs on the dev machine, the event-publisher-proxies ownerref should be either ignored or set to a junk value, so that the functionality doesn't break.
Actual result
Error log tells that deployment cannot be found.
Steps to reproduce
$ k port-forward -n kyma-system svc/eventing-nats 4222
$ make run
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.
The issue is from here where the eventing-controller tries to "look itself up" in the cluster.
One solution could be to move out the setAsOwnerReference out into a separate file, and use build tags (e.g. debug and !debug) to replace the implementation with a dummy one. This way a local make target with the right tag could be used to run the controller in the IDE.
Description
Changes in #11404 showed that local running of the eventing controller doesn't work anymore. Beside setting environment variables the controller had to react at runtime.
Expected result
When the eventing-controller runs on the dev machine, the event-publisher-proxies ownerref should be either ignored or set to a
junk
value, so that the functionality doesn't break.Actual result
Error log tells that deployment cannot be found.
Steps to reproduce
The text was updated successfully, but these errors were encountered: