chore(deps): bump com.puppycrawl.tools:checkstyle from 10.8.0 to 10.12.2 #531
Annotations
10 warnings
charts/irs-helm/templates/deployment.yaml#L1
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
charts/irs-helm/templates/service.yaml#L25
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
charts/irs-helm/templates/configmap-spring-app-config.yaml#L26
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
charts/irs-helm/templates/deployment.yaml#L144
Containers must have the same resource requests set as limits. This is recommended to avoid resource DDoS of the node during spikes and means that 'requests.memory' and 'requests.cpu' must equal 'limits.memory' and 'limits.cpu', respectively
|
charts/irs-helm/templates/deployment.yaml#L1
Images should be specified together with their digests to ensure integrity
|
charts/irs-helm/templates/deployment.yaml#L1
Containers should be configured with an AppArmor profile to enforce fine-grained access control over low-level system resources
|
charts/irs-helm/templates/deployment.yaml#L1
Each namespace should have a LimitRange policy associated to ensure that resource allocations of Pods, Containers and PersistentVolumeClaims do not exceed the defined boundaries
|
charts/irs-helm/templates/deployment.yaml#L1
Each namespace should have a ResourceQuota policy associated to limit the total amount of resources Pods, Containers and PersistentVolumeClaims can consume
|
charts/irs-helm/templates/deployment.yaml#L1
Container should not use secrets as environment variables
|
charts/irs-helm/templates/deployment.yaml#L1
Container should not use secrets as environment variables
|
The logs for this run have expired and are no longer available.
Loading