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

Kubedog show events for linked replicaset #310

Open
samavasi opened this issue Jul 23, 2023 · 5 comments
Open

Kubedog show events for linked replicaset #310

samavasi opened this issue Jul 23, 2023 · 5 comments

Comments

@samavasi
Copy link

Kubedog Support showing linked replicaset events for deployment object (eg to show hints on resourcequota exceeded reason)

@distorhead
Copy link
Member

@samavasi Hi!

Showing events is disabled by default, but you can enable such events for deployment with the following annotation set on deployment:

metadata:
  annotations:
    "werf.io/show-service-messages": "true"

(More info: https://werf.io/documentation/v1.2/reference/deploy_annotations.html#show-service-messages)

Not sure that resourcequota exceeded will be shown in deployment events, but I suppose it should be there, give it a try.
If it does not help then theoretically it is possible to extend show-service-messages behaviour to show events for main resource and linked subordinate resource too.

@samavasi
Copy link
Author

Hi @distorhead thank you for your reply
Indeed the issue is the events are from the subordinate Replicaset so are not visible if I follow the above instructions , I think only pod subordinate events are shown at the moment , any idea if this can be enhanced ?

@ilya-lesikov
Copy link
Member

It might be, we'll look into this.

@ZIK-1337
Copy link

ZIK-1337 commented Dec 7, 2023

It might be, we'll look into this.

@ilya-lesikov
Hi! any movement on this problem? replicaset events are still not outputted.

@ilya-lesikov
Copy link
Member

ilya-lesikov commented Jan 15, 2024

Hi, no, not yet. We were working on a new, more dynamic high-level tracker recently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants