Future Release of Anchore Enterprise v5.0.0
Note
If you are currently using a Postgres version older than 13, please work with your database administrator now to plan and execute the Postgres upgrade in your next convenient maintenance window. We strongly recommend you upgrade Postgres to 13+ using your current Enterprise version and prior to the upgrade to Enterprise 5.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 toEnterprise 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 imageAnchoreCTL
is available within docker.io/anchore/enterprise image todayAnchoreCTL
is the only supported command line tool for interacting with Anchore Enterprise
KAI (Kubernetes Automated Inventory)
will no longer be compatible withEnterprise v5.0.0
. A new version of this agent, calledanchore-k8s-inventory
, is available now and compatible withEnterprise 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 inEnterprise 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
oranchore-k8s-inventory
. In this case, you will need to upgrade your integrations and/or client applications to theEnterprise v5.0.0
compatible versions. A complete list of compatible versions to the upcomingEnterprise v5.0.0
release is found below.
AnchoreCTL Updates
- V2 compatible versions of
AnchoreCTL
will use version numbers associated with Enterprise releases. For example, onceEnterprise v5.0.0
is released, there will be anAnchoreCTL v5.0.0
released. This new version will support only the V2 API and have the same Syft version asEnterprise 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 usingAnchoreCTL v4.9.0
. - Install with:
curl -sSfL https://anchorectl-releases.anchore.io/anchorectl/install.sh | sh -s -- -b /usr/local/bin v4.9.0
- Fully compatible with the V2 API available within
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.
Integration | Recommended V2 API Compatible Version |
---|---|
AnchoreCTL | v4.9.0 |
anchore-k8s-inventory | v1.1.1 |
anchore-ecs-inventory | v1.2.0 |
Kubernetes Admission Controller | v0.5.0 |
Jenkins Plugin | v1.1.0 |
Harbor Scanner Adapter | v1.2.0 |
enterprise-gitlab-scan | TBD |