Skip to main content
Every Aviatrix feature moves through GA, Preview, and Early Access (EA) stages before general release. Each stage gives you a defined level of support and stability, and an opportunity to try new capabilities and provide feedback before they mature. Every Aviatrix feature falls into one of three modes in the following table:

​
General Availability (GA) Features

GA features have passed Aviatrix’s standard release validation and are fully supported and safe for deployment in production environments. All Aviatrix features are GA unless otherwise mentioned.

​
Preview Features

Preview features are functional, supported, and available to all Aviatrix users. They are in the final stages of development, with a high likelihood of becoming GA. Preview features are an opportunity for you to evaluate upcoming capabilities and share feedback that shapes the final product.

​
Early Access (EA) Features

EA features are in active development and available to a select group of Aviatrix users upon request. They let you influence the direction of a feature in its earliest stages. EA features are not guaranteed to advance to Preview or GA.

​
Adopt Preview and EA Features Safely

Not all preview features carry the same scope of impact on your environment. Some are read-only visibility features that you can enable anywhere. Others modify traffic behavior and are best tried on a single Gateway first. The Feature Classification table classifies every Preview and EA feature so you can choose a safe starting scope for each one.

​
Impact Scope Levels

Read and understand the following legends before going to the Feature Classification table.

​
Feature Classification

Transit Gateways carry traffic for multiple VPCs and Transit domains. Any inline feature enabled on a Transit Gateway carries a broader impact scope than the same feature on a Spoke.
The feature classifications assume that you follow the guidance to start on Spoke Gateways. If you enable a feature on a Transit Gateway, consider it as one level broader in scope.
Several DCF features can be configured with policies in logging-only mode (no enforcement action). While logging mode is lower risk than enforcement, DCF still inserts into the data path when enabled.Logging mode is a good first step for observation, but it is not the same as no impact. The feature classifications account for this.
The following table classifies every Preview and EA feature so you can adopt each one with confidence.
For DCF features, Stage and GA Version mirror the per-version history maintained in the DCF Supported Capabilities table, which is the source of truth if the two ever disagree. This table adds Impact Scope and Minimum Safe Scope guidance that the capabilities table does not cover.
Version Introduced is the first Controller version where the feature became available in its current stage. GA Version is the target or actual version where the feature graduates to GA. A dash indicates the value is not yet determined.

​
Feedback

Preview features are available for you to try, and your feedback directly shapes what becomes GA. If you have questions, encounter unexpected behavior, or want to share suggestions:
  • Preview features: supported through standard Aviatrix support channels.
  • Early Access features: contact your Aviatrix account team for dedicated support.
  • In CoPilot: use the feedback button on any preview feature page.