Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do
not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
The goal of this feature is to add reporting of the actual value and limits in the policy model after the cluster evaluation. This makes most sense for scalability checks, when user would like to know the actual values and limits, in the evaluation report, even when policy is valid.
From the user perspective, the current console output for a valid scalability policy looks like this:
🔎 [Scalability] gke.scalability.pods: Number of PODs in a cluster
- projects/gke-policy-demo/locations/europe-central2/clusters/cluster-waw [ OK ]
With the feature implemented, it could look like below:
🔎 [Scalability] gke.scalability.pods: Number of PODs in a cluster
- projects/gke-policy-demo/locations/europe-central2/clusters/cluster-waw [ 120 out of 300k ]
The 120 out of 300k would reman printed in a green colour.
In a JSON report, the policy will be valid isValid: true but new fields, actuals and limit will be present.
Community Note
Description
The goal of this feature is to add reporting of the actual value and limits in the policy model after the cluster evaluation. This makes most sense for scalability checks, when user would like to know the actual values and limits, in the evaluation report, even when policy is valid.
From the user perspective, the current console output for a valid scalability policy looks like this:
With the feature implemented, it could look like below:
The
120 out of 300kwould reman printed in a green colour. In a JSON report, the policy will be validisValid: truebut new fields, actuals and limit will be present.References
N/A