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
Is your feature request related to a problem? Please describe.
We have a use case where we own a set of multi-tenant clusters, being a central team. Clusters have different namespaces owned by different teams.
Central team may want to get a general overview report of the cluster status. Each tenant team can run themselves their popeye report to check their own status and fix their namespace.
Still, central team wants to provide the ability to tenant teams to annotate a certain resource, so checks are skipped for it on both runs:
Popeye runs from the tenant team (as they know why they want to skip it), so their score is not impacted by that resource
Also the central team runs, as they can calculate the same score as the tenant team wants, without active communication between both.
Describe the solution you'd like
Specific resources (any) could be annotated with an annotation like: popeyecli.io/skip-checks: "true"
which will raise an info message stating "Resource xx/yyyy has been skipped"
Describe alternatives you've considered
A clear alternative could be that the central teams have a public config file and the tenant team can trigger a PR with a change on the excludes section, but still, I prefer the annotation as an info is also notifying the central team the resources that are proactively ignored.
Additional context
The text was updated successfully, but these errors were encountered:
I like the suggestion. One thing to think about is a way to make the annotation more expressive (than just binary true/false), e. g. to disable certain checks, but not others.
@marians@danibaeyens Thank you both for piping in. I like the concept but I think it would be tough to convey variations or be as expressive as a spinach config. Another issue to consider here is what if you want to run popeye wide open?
@derailed the reason for this issue was the explanation here: #144 (comment)
Worst case, I might recommend teams to use the grafana dashboard to pick and choose their score depending on the rules they want to watch.
Is your feature request related to a problem? Please describe.
We have a use case where we own a set of multi-tenant clusters, being a central team. Clusters have different namespaces owned by different teams.
Central team may want to get a general overview report of the cluster status. Each tenant team can run themselves their popeye report to check their own status and fix their namespace.
Still, central team wants to provide the ability to tenant teams to annotate a certain resource, so checks are skipped for it on both runs:
Describe the solution you'd like
Specific resources (any) could be annotated with an annotation like:
popeyecli.io/skip-checks: "true"
which will raise an info message stating
"Resource xx/yyyy has been skipped"
Describe alternatives you've considered
A clear alternative could be that the central teams have a public config file and the tenant team can trigger a PR with a change on the excludes section, but still, I prefer the annotation as an info is also notifying the central team the resources that are proactively ignored.
Additional context
The text was updated successfully, but these errors were encountered: