CubeCMP 2.1.0 Release

Release overview

CubeCMP 2.1.0 (released June 12, 2026) introduces a production-ready NFV networking layer that includes multi-network instance attachment, spine network management, and router lifecycle APIs. It features a rebuilt v2 firewall system with policy enforcement for all types of workloads, including instances, apps, ASGs, Kubernetes clusters, and load balancers. This release adds support for RKE2 clusters, a tenant provisioning API, v1 to v2 database migration, and cross-provider resource analysis APIs.

Upgrading from version 2.0.x is non-disruptive. The v1 firewall records, private network schemas, and router configurations are migrated automatically upon first startup.

For a full list of changes at the commit level, refer to the CubeCMP changelog.

New features

NFV and advanced networking

CubeCMP 2.1.0 provides a complete Network Functions Virtualization (NFV) layer that enables enterprise-grade, multi-network topologies.

• Multiple private networks per workload: Workloads can now be attached to multiple private networks simultaneously. Support is provided for both manually specified and automatically assigned IP addresses.
• Spine network management: Site admins can create, edit, and delete spine networks via the portal, with CIDR overlap validation and live status indicators.
• Router lifecycle: Full CRUD for routers, including uplink attach and detach, NAT toggle, and static route reconciliation on network changes.
• CIDR overlap enforcement: Enforces overlap checks against both spine and provider networks during the creation and attachment of networks and routers.
• Load balancer flavor selection: When creating a load balancer, you can now specify a load balancer flavor.

Native RKE2 support

Full support for RKE2 clusters alongside existing RKEv1 infrastructure.

• RKE2: Cluster creation, scaling, and deletion.
• Multi-provider cluster management: Support management of both RKEv1 and RKE2 clusters during service upgrade and migration.
• Migration: Automated migration from RKEv1 to RKE2 during CubeCMP 2.1.0 upgrade.

Resource analysis

CubeCMP 2.1.0 provides comprehensive cloud resource analysis and cost tracking across projects and providers.

• Cloud admin resource analysis: Site admins can view cross-project resource consumption trends, rankings, and cost breakdowns.
• Project admin resource analysis: Project-level analysis with provider filtering, time-range scoping, and amount and ranking APIs.
• Billing pagination: Billing reports now paginate correctly using the v2 page contract.
• Unpriced resource rows: Resource usage rows without a price are persisted for resource analysis visibility rather than being silently dropped.

Platform and operations

• RKE2 cluster support: Full CRUD for RKE2 clusters and node pools alongside existing RKE1 support.
• Demo billing and usage seed: New demo-seed tool generates realistic billing and usage data for demos.
• Project pre-check on create: OpenStack availability is verified before a v2 project creation is committed.
• Event audit improvements: Remote_ip and user info now populate correctly on firewall, volume-clone, alert, and cloud-admin events.

Internationalization

Comprehensive i18n coverage added across the portal in this release cycle:

• All project-admin pages: Instances, volumes, clusters, apps, ASGs, load balancers, networking, billing, events, and settings.
• All site-admin pages: Alerts, notifications, billing, policies, cloud providers, customization tabs, projects, and summary.
• NFV-specific pages: Spine networks, routers, and firewall detail tabs.

Compatibility

CubeCMP requires App Framework v2 for RKE2 support. CubeCMP 2.1.0 is compatible with the following deployment scenarios.

Compatibility with CubeCOS 3.1.0

CubeCOS 3.1.0 deploys the native App Framework v2, which is used with CubeCMP 2.1.0 to support RKE2.

Deployment scenario	Fresh install CubeCMP 2.0.0	Fresh install CubeCMP 2.1.0	Upgrade CubeCMP 2.0.0 → 2.1.0	Create App Framework v2 + fresh install CubeCMP
Fresh CubeCOS 3.1.0 deployment (App Framework v2)	Supported	Supported	Supported	N/A
CubeCOS 3.0.0 upgraded to 3.1.0 (App Framework v1 retained)	Supported	Supported	Supported	Supported

Deployment information

For a CubeCOS 3.0.0 deployment that has been upgraded to 3.1.0, you can create a new App Framework v2 instance alongside the existing v1 instance. Then, you can perform a fresh installation of either CubeCMP 2.0.0 or 2.1.0 on top of it.

Compatibility with CubeCOS 3.0.0

CubeCOS 3.0.0 ships with App Framework v1.

Deployment scenario	Fresh install CubeCMP 2.0.0	Fresh install CubeCMP 2.1.0	Upgrade CubeCMP 2.0.0 → 2.1.0
Fresh CubeCOS 3.0.0 deployment (App Framework v1)	Supported	Supported	Supported

For deployment support or compatibility details, contact Bigstack.

Known issues

1. During system upgrades, when the App-fw undergoes migration or reboots, it intermittently triggers an unexpected alteration in MongoDB configurations (#832).
2. Instance export fails unexpectedly (#855).
3. Unable to resize AWS-based instances (#876).
4. CMP Firewall Port Range Display Anomaly (#877).
5. Logical flaw in the Auto-Scaling Group (ASG) capacity calculation when VMs enter a suspend state due to lifecycle expiration (#911).

Feature deprecation and EOL

The RKEv1 cluster is being deprecated in this release.

To continue using CubeCMP and support RKE2 natively, upgrade to CubeCOS 3.1.0 with AppFramework 2.0.

More information

For comprehensive details about CubeCMP 2.1.0, visit the CubeCMP product documentation.