Skip to content

Anchore Engine Helm Chart📜

This chart deploys the Anchore Engine docker container image analysis system + several Big Bang modifications as desired. Anchore Engine requires a PostgreSQL database (>=9.6) which may be handled by the chart or supplied externally, and executes in a service based architecture utilizing the following Anchore Engine services: External API, SimpleQueue, Catalog, Policy Engine, and Analyzer.

This chart can also be used to install the following Anchore Enterprise services: GUI, RBAC, Reporting, Notifications & On-premises Feeds. Enterprise services require a valid Anchore Enterprise License as well as credentials with access to the private DockerHub repository hosting the images. These are not enabled by default.

Each of these services can be scaled and configured independently.

See Anchore Engine for more project details.

NOTE: Big Bang’s implementation is designed to be enabled and consumed from within a customer implementation of the Big Bang release. It is fully functional as a standalone Helm install, but Big Bang will enable best integration for Big Bang “extras” and ease of use.

Chart Details📜

The chart is split into global and service specific configurations for the OSS Anchore Engine, as well as global and services specific configurations for the Enterprise components. Additionally included are Big Bang specific configs.

  • The top section provides customizable Big Bang values for SSO, Istio, and automating the license secret creation for enterprise.
  • The anchoreGlobal section is for configuration values required by all Anchore Engine components.
  • The anchoreEnterpriseGlobal section is for configuration values required by all Anchore Engine Enterprise components.
  • Service specific configuration values allow customization for each individual service.

For a description of each component, view the official documentation at: Anchore Enterprise Service Overview

Installing the Anchore Engine Helm Chart📜

Install Standalone📜

First clone this repository, then navigate to it from your terminal. Assuming you have a k8s cluster created and pointed to in your kubeconfig, use Helm to install the chart.

helm upgrade -i anchore chart -n anchore --create-namespace

NOTE: As with any other Helm chart there is an included values file that can be customized to your needs prior to installation.

Install with Big Bang📜

Assuming you have read through documentation on how to use Big Bang and have it set up in your k8s cluster, enabling Anchore can be done through a change to your values configmap.yaml.

addons:
  anchore:
    enabled: true

This will enable the “basic” install of Anchore with no enterprise components.

At this point you can also include other values to customize your install. The main admin password must be updated from its default in any environment. In your secrets.enc.yaml file you can include the below and encrypt them (or simply include in your configmap in development environments):

stringData:
  values.yaml: |-
    addons:
      anchore:
        adminPassword: "my-super-secret-password"

Adding Enterprise Components📜

The following features are available to Anchore Enterprise customers. Please contact the Anchore team for more information about getting a license for the enterprise features. Anchore Enterprise Demo

  • Role based access control
  • LDAP integration
  • Graphical user interface
  • Customizable UI dashboards
  • On-premises feeds service
  • Proprietary vulnerability data feed (vulnDB, MSRC)
  • Anchore reporting API
  • Notifications - Slack, GitHub, Jira, etc
  • Microsoft image vulnerability scanning

Enabling Enterprise Services📜

Once you have decided on Enterprise services to make use of, make sure to add the proper configs to your configmap.yaml and as needed any secret values to the secrets.enc.yaml file. Big Bang provides by default a good setup of services when you enable enterprise.

The below walks through a minimal configuration to enable Global Enterprise and externalize dependencies as is often desired in a prod environment.

Anchore Enterprise requires a license secret to be created as well as enabling the Enterprise values through Helm. Big Bang has implemented automated creation of the license secret as follows.

Within an encrypted “values” file - secrets.enc.yaml - add the following to set the license to be added as a secret:

stringData:
  values.yaml: |-
    addons:
      anchore:
        enterprise:
          licenseYaml: |
            first line of license:
              more license lines:...
            end of license:

P1 has a license that can be used for dev - this license is located here. To make use of it you will need to SOPS decrypt it with your AWS Coder credentials.

Once you have added the license to this location make sure to re-encrypt your secret file.

In your un-encrypted values file - configmap.yaml add the following to enable Enterprise Global:

addons:
  anchore:
    enterprise:
      enabled: true

Handling Dependencies📜

Anchore relies on a single Postgres instance by default, as well as an additional Postgres database and Redis server if certain Enterprise configs are enabled. For development work and non-production workflows you can use the embedded dependency charts to automatically spin these dependencies up. In this case you don’t need to provide any values.

stringData:
  values.yaml: |-
    addons:
      anchore:
        database:
          host: ""
          port: ""
          username: ""
          password: ""
          database: "" 
          feeds_database: ""

Big Bang does not currently provide a production solution to be utilized, so it is recommended that you connect to existing external instances. Using the embedded instances in production is AT YOUR OWN RISK.

To externalize the dependency on postgres see the values below. Since some of these values are sensitive they should be added to your encrypted secrets.enc.yaml file (be sure you don’t name your databases with hyphens or psql will throw errors).

stringData:
  values.yaml: |-
    addons:
      anchore:
        database:
          host: "testing.amazon.rds.com"
          port: "5432"
          username: "username"
          password: "password"
          database: "anchore" 
          feeds_database: "anchorefeeds"

By default, when using an external postgres setup, the feeds_database will use the same username, password, host, and port as the main database. This is for streamlined ease of use for customers. However, if you’d like to configure the feeds_database with separate credentials, you can do so by overriding the upstream values (be sure you don’t name your databases with hyphens or psql will throw errors):

stringData:
  values.yaml: |-
    addons:
      anchore:
        database:
          host: "testing.amazon.rds.com"
          port: "5432"
          username: "username"
          password: "password"
          database: "anchore" 
          feeds_database: ""
        values:
          anchore-feeds-db:
            enabled: false
            postgresUser: "user2"
            postgresPassword: "password2"
            postgresDatabase: "anchorefeeds"                                  
            externalEndpoint: "postgres-postgresql.postgres.svc.cluster.local:5432"

For production, you may want to externalize your Redis instance for Anchore Enterprise UI:

stringData:
  values.yaml: |-
    addons:
      anchore:
        redis:
          host: "redis.mydomain.com"
          port: "6379"
          password: "password"

Configuring Istio📜

Istio can be configured to utilize your desired gateway(s) and host(s). To configure istio, pass the following options to the Anchore values:

stringData:
  values.yaml: |-
    addons:
      anchore:
        values:
          istio:
            enabled: true
            ui:
              # Toggle vs creation
              enabled: true
              annotations: {}
              labels: {}
              gateways:
                - istio-system/<INSERT_GATEWAY_HERE>
              hosts:
                - "<INSERT_ANCHORE_UI_HOST_HERE>.{{ .Values.hostname }}"
            api:
              # Toggle vs creation
              enabled: true
              annotations: {}
              labels: {}
              gateways:
                - istio-system/<INSERT_GATEWAY_HERE>
              hosts:
                - "<INSERT_ANCHORE_API_HOST_HERE>.{{ .Values.hostname }}"

Enable SSO📜

Big Bang has provided an automated way to configure SSO with Keycloak via the Helm chart. To enable and configure SSO follow the instructions in the main KEYCLOAK document.

Installing on OpenShift📜

The upstream chart README provides additional details on how to deploy to OpenShift. Necessary values are also included in the values file in this repo.

Upstream Chart Updates📜

See the anchore-engine CHANGELOG for updates to the upstream chart. Big Bang will fork from these updates and add necessary additions, and then a new tagged release will be provided and Big Bang will be updated to use the new release.