- Navigating the Future: Wi-Fi 7 as the Multi-Lane Highway of Connectivity
- Data Shows You’ll Encounter A Deepfake Today—Here’s How To Recognize It | McAfee Blog
- NordLayer set to release a new security-focused browser for the enterprise
- 10 bugs still haunt Windows 11 24H2 despite multiple patches
- DragonForce Ransomware Hits Saudi Firm, 6TB Data Stolen
StarlingX bridges IPv4-IPv6 gap with dual-stack networking support

IPv6 dual-stack enables distributed cloud architectures
Dual-stack IPv4 and IPv6 networks can be set up in StarlingX cloud deployments in several ways.
Váncsa said that users are now able to configure the platform to use both IPv4 and IPv6 address spaces without service disruptions. Once the first address pool is allocated to a network upon creation it will become the primary, which cannot be later removed. The secondary address pool can be dynamically allocated or removed to transition the system between dual-stack and single-stack modes as needed. Users can perform additional configuration on the deployment, including DNS setup and load balancing based on the equipment used in their environment and the demands of their particular use cases.
Of note, Váncsa explained that the flagship feature in StarlingX is the Distributed Cloud architecture model, where users can deploy sub-clouds in remote locations to be managed from a central site. “As users upgrade to the latest version of the platform, they will now be able to configure sub-clouds to take advantage of the dual-stack networking configuration,” she said.
StarlingX gets a new ‘safe’ Harbor
Another key addition to the StarlingX 10 updates is the integration of the Harbor container registry. Cloud-native deployments largely rely on the use of containers. A container registry is a central repository where an operator can pull container images for cloud deployment.
“Security has been a high priority for the StarlingX community, which drove the decision to integrate the Harbor container registry into the platform as well,” Váncsa said.
She noted that the Harbor provides various features to improve the security of how StarlingX handles container images, open policy agents (OPA), and Helm charts. OPA is an open-source policy engine used in Kubernetes deployments to define and write policy for containers. Helm charts are a widely used open-source deployment technology for containers in Kubernetes.