0.3.5-0.1.0 • Published 5 years ago

@helm-charts/banzaicloud-stable-anchore-policy-validator v0.3.5-0.1.0

Weekly downloads
1
License
MIT
Repository
-
Last release
5 years ago

@helm-charts/banzaicloud-stable-anchore-policy-validator

A Helm chart for anchore-policy-validator admission controller

FieldValue
Repository Namebanzaicloud-stable
Chart Nameanchore-policy-validator
Chart Version0.3.5
NPM Package Version0.1.0
replicaCount: 1
logVerbosity: 1
apiService:
  group: admission.anchore.io
  version: v1beta1
image:
  repository: banzaicloud/anchore-image-validator
  tag: 0.3.2
  pullPolicy: IfNotPresent
service:
  name: anchoreimagecheck
  type: ClusterIP
  externalPort: 443
  internalPort: 8443
externalAnchore:
  anchoreHost: ''
  anchoreUser: ''
  anchorePass: ''
resources: {}

## Node selector
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
nodeSelector: {}

## Affinity
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
affinity: {}

## Tolerations
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []

Anchore policy validator

This chart deploys an admission-server that is used as a ValidatingWebhook in a k8s cluster. If it's working, kubernetes will send requests to the admission server when a Pod creation is initiated. The server checks the image, which is defined in PodSpec, against configured Anchore-engine API. If the API responds with an error, that the image is not valid according to defined policy, k8s will reject the Pod creation request.

Installing the Chart

$ helm repo add banzaicloud-stable http://kubernetes-charts.banzaicloud.com/branch/master
$ helm repo update

Deploying anchore-policy-validator using external Anchore-engine service:

$ helm install --name <name> --set externalAnchore.anchoreHost=<my.anchore.host>  --set externalAnchore.anchoreUser=<username> -set externalAnchore.anchorePass=<password> banzaicloud-stable/anchore-policy-validator

During deploying this chart, it's creating predefined policy bundles and activates AllowAll by default.

Policy bundles

PolicyNameDescription
AllowAllAllow all images to deploy
RejectCriticalReject deploying images that contain critical vulnerabiliy
RejectHighReject deploying images that contain high vulnerabiliy
BlockRootBlock deploying images that using root as effective user
DenyAllDeny all imagest to deploy

Configuration

The following tables lists configurable parameters of the anchore-policy-validator chart and their default values.

ParameterDescriptionDefault
replicaCountnumber of replicas1
logVerbositylog verbosity level8
apiService.groupgroup of registered api serviceadmission.anchore.io
apiService.versionversion of registered api servicev1beta1
image.repositoryadmission-server image repobanzaicloud/anchore-image-validator
image.tagadmission-server image tag0.3.0
image.pullPolicyadmission-server image pull policyIfNotPresent
service.namevalidation sevice nameanchoreimagecheck
service.typevalidation service typeClusterIP
service.externalPortvalidation service external port443
service.internalPortvalidation service external port443
externalAnchore.anchoreHostexternal anchore-engine host""
externalAnchore.anchoreUserexternal anchore-engine username""
externalAnchore.anchorePassexternal anchore-engine password""