Push Charts to helm-charts-registry manually with specified version #1
Annotations
10 warnings
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/deployment.yaml#L20
Check if containers are running with low UID, which might cause conflicts with the host's user table.
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/configmap.yaml#L4
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/ingress.yaml#L3
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/service.yaml#L4
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/realm-secret.yaml#L4
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/deployment.yaml#L2
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/secret.yaml#L4
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/deployment.yaml#L20
Images should be specified together with their digests to ensure integrity
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/templates/deployment.yaml#L14
Containers should be configured with an AppArmor profile to enforce fine-grained access control over low-level system resources
|
|
Scan with kics:
charts/dbildungscloud-iam-keycloak/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
|
Loading