forked from kumahq/kuma
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.kube-linter.yaml
34 lines (33 loc) · 1009 Bytes
/
.kube-linter.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
checks:
addAllBuiltIn: true
exclude:
- "unset-cpu-requirements"
# Look at https://github.com/kumahq/kuma/issues/8908 to reenable all these
- dnsconfig-options
- access-to-secrets
- minimum-three-replicas
- no-liveness-probe
- no-readiness-probe
- required-label-owner
- required-annotation-email
- access-to-create-pods
- no-node-affinity
- non-isolated-pod
- no-rolling-update-strategy
- writable-host-mount
- exposed-services
- use-namespace
customChecks:
- name: "unset-cpu-requests"
description: "Indicates when containers do not have CPU requests set."
scope:
objectKinds:
- DeploymentLike
remediation: >-
Set CPU requests for your container based on its requirements.
Refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits for details.
template: "cpu-requirements"
params:
requirementsType: "request"
lowerBoundMillis: 0
upperBoundMillis: 0