-
Notifications
You must be signed in to change notification settings - Fork 332
Listening for custom resource events #47
Comments
It should work, it should just not be able to read the additional labels ore metadata of them since they are not available in default view role. I need to reproduce it, I might have overlooked it before because when I run it from my IDE, it always runs with the administrator role. |
That was my understanding as well. Alas, it doesn't work, at least not with the roles in the |
I tested it with installing Tekton to my Minikube. It gets dumped, I'm not really sure what is going on. Here are the test logs:
I also logged the involved object's name, I don't think it's a rights issue. Which type of Kubernetes cluster you run? |
I can also confirm logging to stdout also worked in Minikube with that role:
With this config:
|
i have a similar issue with the default config from deploy directory except the change in the elastic search url apiVersion: v1 with a custom pod running in another namespace , the corresponding events for those pods are not pushed to ES below is the repo i used without any changes (except for the elasticsearch URL) https://github.com/opsgenie/kubernetes-event-exporter/tree/deployment-and-readme-fix/deploy |
It's not obvious from the code why the watcher isn't getting events about custom resources, but it doesn't look like it's a configuration issue. Could you please clarify if that's the expected behaviour? Here's an example event:
Other standard events are successfully captured.
The text was updated successfully, but these errors were encountered: