Skip to content

release(1.6.0-RC4): merge release to main #56 #254

release(1.6.0-RC4): merge release to main #56

release(1.6.0-RC4): merge release to main #56 #254

Triggered via push July 31, 2023 14:34
Status Success
Total duration 1m 45s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

kics.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-backend-appmarketplace.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-backend-registration.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-frontend-assets.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-frontend-registration.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/cronjob-backend-portal-maintenance.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-backend-administration.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-backend-notification.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-frontend-portal.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/cronjob-backend-processes.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests
[MEDIUM] CPU Limits Not Set: charts/portal/templates/deployment-backend-services.yaml#L1
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests