What's New in the Apcera Platform

This section summarizes what is new in Apcera Platform releases, including long-term support (LTS) and maintenance releases.

2.4.2 Maintenance Release

Apcera Platform release 2.4.2 is a maintenance release that includes bug fixes. See the release notes for complete release details.

2.4.1 Maintenance Release

Apcera Platform release 2.4.1 is a maintenance release that includes a Linux security kernel patch. See the release notes for complete release details.

2.4.0 LTS Release

Apcera Platform 2.4.0 is a major release that includes the following features. See also the release notes and upgrade paths.

Expanded IAM support

Apcera Platform release 2.4 adds support for Keycloak and Active Directory for cluster user identity and access management (IAM).

Enhanced auditing capabilities

The Audit Log is enhanced to provide richer and deeper metadata about cluster operations to improve auditing capabilities, including policy requests and violations. In addition, there is a new audit “payload" field and enhancements to APC and the Web Console to view audit payload fields.

Improvements for virtual networking

Apcera Platform release 2.4 improves virtual networking by upgrading Open vSwitch (OVS). (If you are upgrading a cluster to 2.4, jobs in the virtual networks will be restarted.)

In addition, release 2.4 supports Virtual Extensible LAN (VXLAN) as the default tunneling technology for new clusters. Existing clusters continue to use Generic Routing Encapsulation (GRE) and must be updated and rebooted to use VXLAN. Refer to the enabling VXLAN documentation for migration instructions.

Support for GRE is deprecated. If you do not enable and migrate to VXLAN now, you will be required to for the next long term support (LTS) release.

Expanded Docker support

Apcera Platform release 2.4 expands its first class support for Docker images and jobs by offering:

Policy and security updates

Cluster deployment improvements

Expanded platform support for Enterprise Edition

Apcera Platform release 2.4 expands public cloud support for installing a full EE cluster to include Microsoft Azure and Google GCE.

In addition, Apcera-provided modules are updated to Terraform 0.7.x and the BareOS documentation is updated.

Community Edition enhancements

There is a new version of the apcera-setup installer (2.2.1) for the Apcera Platform Community Edition. The installer is updated with usability enhancements and support for the AWS us-east-2 region.

Upgrade paths

You can upgrade directly to release 2.4.0 from Apcera Platform versions 2.2.2 or 2.2.3. No other upgrade paths are supported. You must use Orchestrator 0.5.3 to deploy the 2.4.0 release and take advantage of new deployment features.

Review the release notes and upgrade instructions before upgrading.

2.2.x Maintenance Releases

2.2.3 Maintenance Release

Apcera Platform release 2.2.3 is a critical security release. See the release notes for complete release details.

2.2.2 Maintenance Release

Apcera Platform release 2.2.2 is a maintenance release that includes bug fixes. See the release notes for complete release details.

2.2.1 Maintenance Release

Apcera Platform release 2.2.1 is a maintenance release that mainly includes bug fixes. This release also includes support for using VXLAN to create virtual networks instead of GRE. See the release notes for complete release details.

2.2.0 LTS Release

Apcera Platform release 2.2 includes the following features. Check out the release notes for release details.

Web Console Improvements

Continued maturity of the web console, including:

  • Data Tables editor for adding and updating policy data and scaling policy.
  • Integrated login page. (If you are using Google Auth, you may need to update the redirect URLs.)
  • Context-sensitive help and inline documentation.

Policy Scaling

Enhancements to the the policy language and engine help you scale large policy sets, including:

To get started, check out the Policy Data Tutorial.

Application Tokens

Using the Application Tokens feature, you can allow a job running in the Apcera Platform to receive authentication JSON Web Tokens (JWT) that the job can use to perform actions against the public HTTP API using APC commands.

To get started, check out the App Token Tutorial.

Application Events

Using the Application Events feature, users and systems can subscribe to application events by job or by namespace.

To use application events, you will need to add the events-server component to your cluster.conf file. Refer to the sizing guidelines and upgrade instructions.

SMB Persistent Storage

You can now use SMB 2.0 for persistent file storage with customized mount points. SMB allows for finer-grained authentication than NFS.

Support for AWS EFS

Amazon Elastic File System (Amazon EFS) provides simple, scalable file storage for use with Amazon EC2 instances in the AWS Cloud. You can use Apcera's NFS Service Gateway to access AWS EFS storage volumes within containers. See File Share Services - Amazon Elastic File System (AWS EFS).

Multi-resource manifests

The multi-job manifest syntax is expanded to support virtual networks and service creation and binding as first class objects. The feature is renamed to multi-resource manifests.

Job links between container instances are now load balanced for improved job scaling.

EE Cluster Encryption (BETA)

End-to-end cluster encryption using IPsec mesh tunnels for all runtime traffic between Apcera component hosts. This feature is available for BETA use.

EE Cluster HA

Required components can now be deployed in multiple for highly available production deployments.

EE Expanded Platform Support and Tooling

Additional platforms supported for deployment of the Enterprise Edition.

CE Enhancements

2.0.0 LTS Release

Apcera Platform release 2.0 includes the following features. Check out the release notes for details.

Web Console Improvements

Policy Simulator

Use the policy simulator to audit existing policy and test new policy, including hypotheticals.

Highly Available NFS

Integration with Gluster for full HA NFS.

Multi-job Manifests

Compose and orchestrate workloads using multi-job manifests.

Flex-Auth Servers

Individual, scalable auth server components for integrating with supported identity providers.

To use Flex Auth, you will need to add the appropriate flex-auth-server component to your cluster.conf file. Refer to the sizing guidelines and upgrade instructions.

EE Expanded Platform Support and Tooling

New Community Edition

Deploy in 15 minutes a small-scale cluster on AWS, VirtualBox, VMware, OpenStack, and vSphere.