Helm chart is reporting a missing PodDisruptionBudget when replicas count is not defined
Which version of kube-score are you using?
kube-score version: 1.16.1
What did you do?
I run kube-score against bitnami/sealed-secrets helm chart and I got an issue related to a missing PodDisruptionBudget.
When I looked into the deployment manifest, I noticed that the replicas field is not set, and because of that, the test is failing, which is not expected, because the value will be 1 after the deployment.
if deployment.Spec.Replicas != nil && *deployment.Spec.Replicas < 2 {
score.Skipped = true
score.AddComment("", "Skipped because the deployment has less than 2 replicas", "")
return
}
What did you expect to see?
Test should be skipped
What did you see instead?
[CRITICAL] Deployment has PodDisruptionBudget
· No matching PodDisruptionBudget was found
It's recommended to define a PodDisruptionBudget to avoid
unexpected downtime during Kubernetes maintenance operations, such
as when draining a node.
zegl / kube-score
Kubernetes object analysis with recommendations for improved reliability and security. kube-score actively prevents downtime and bugs in your Kubernetes YAML and Charts. Static code analysis for Kubernetes.
2.8k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too