Future Release of Anchore Enterprise v5.0.0

For detail steps on migrating to the v5.0.0 release, please see 5.0 Migration Guide.

Upgrade Requirements

  • Postgres database major version must be 13 or greater in order to upgrade to Enterprise v5.0.0
    • Our current minimal allowed Postgres version is 9.6 which is no longer supported by Postgres
    • Postgres 13 is significantly more performant than prior versions and provides additional schema update features that enable a better Enterprise upgrade experience.
  • Your current Enterprise release must be v4.0.0 or greater in order to upgrade to Enterprise v5.0.0
    • If you are currently running a release older than v4.0.0, please upgrade to an Enterprise release in the v4.x series
  • A new Enterprise Helm Chart will be available shortly for review. The Enterprise Helm Chart is required for use with Enterprise v5.0.0.

Deprecations

  • The anchore-cli has been deprecated and will be removed from the docker.io/anchore/enterprise image
    • AnchoreCTL is available within docker.io/anchore/enterprise image today
    • AnchoreCTL is the only supported command line tool for interacting with Anchore Enterprise
  • KAI (Kubernetes Automated Inventory) will no longer be compatible with Enterprise v5.0.0. A new version of this agent, called anchore-k8s-inventory, is available now and compatible with Enterprise v4.7.0. You may start to migrate to this new agent today.
  • Support for REM (Remote Execution Manager) has been deprecated. It will no longer be supported in Enterprise v5.0.0.

Additional Changes

  • The Enterprise v5.0.0 release will have multiple updates to the public API. Many of these changes will not be backwards compatible. This will only be impactful if you are currently accessing Anchore Enterprise directly via our public APIs. For more information, please see Migrating from API V1 to V2.
  • Most customers access Anchore Enterprise via one or more of our custom integrations or clients such as Enterprise UI, AnchoreCTL or anchore-k8s-inventory. In this case, you will need to upgrade your integrations and/or client applications to the Enterprise v5.0.0 compatible versions. A complete list of compatible versions to the upcoming Enterprise v5.0.0 release is found below.

AnchoreCTL Updates

  • V2 compatible versions of AnchoreCTL will use version numbers associated with Enterprise releases. For example, once Enterprise v5.0.0 is released, there will be an AnchoreCTL v5.0.0 released. This new version will support only the V2 API and have the same Syft version as Enterprise v5.0.0.
  • AnchoreCTL v4.9.0 is available now!
    • Fully compatible with the V2 API available within Enterprise v4.9.x.
    • Once you have upgraded to Enterprise v4.9.x, you should start using AnchoreCTL v4.9.0.
    • Install with:
      curl -sSfL  https://anchorectl-releases.anchore.io/anchorectl/install.sh  | sh -s -- -b /usr/local/bin v4.9.0
      

Compatible Integrations

  • Integrations have been released that support Enterprise V2 API.
  • Once you upgrade your deployments to Enterprise v4.9.x, you should upgrade all integrations to the compatible versions which support V2 API. Doing this now will minimize the impact of the 5.0 upgrade on clients.
IntegrationRecommended V2 API Compatible Version
AnchoreCTLv4.9.0
anchore-k8s-inventoryv1.1.1
anchore-ecs-inventoryv1.2.0
Kubernetes Admission Controllerv0.5.0
Jenkins Pluginv1.1.0
Harbor Scanner Adapterv1.2.0
enterprise-gitlab-scanTBD
Last modified November 16, 2023