Botsman EE 3.4 adds IPv6 and Kubernetes operations updates

On 7 July 2026, Astra Group announced Botsman EE 3.4, its container-management platform release. The principal networking change is IPv6 support. The release also covers external authentication, security, distributed storage and the administration interface.

What the release contains

IPv6 support expands deployment options for Kubernetes clusters in enterprise and telecom networks. The primary source does not specify the full coverage of dual-stack scenarios, network plugins and external load balancers, so each topology still needs a compatibility test.

The external identity-provider workflow now includes a connection test. This should expose configuration errors before cluster access becomes dependent on the new identity system.

Other confirmed changes include:

• a redesigned password generator;
• removal of unauthenticated access to account-policies settings;
• an upgrade of distributed storage to Longhorn 1.8.2;
• clearer pod, resource and add-on states;
• in-form editing for some configuration-import conflicts.

Why IPv6 needs an end-to-end test

IPv6 in the control panel does not make the entire application path ready. A pilot should verify:

1. addressing for nodes, pods and services;
2. CNI, ingress-controller and load-balancer compatibility;
3. DNS records and A/AAAA resolution order;
4. network policies for both protocols;
5. routes to external databases, storage and APIs;
6. logs, metrics and traces over both protocols;
7. recovery from an incorrect dual-stack configuration.

Firewall policy deserves special attention. IPv6 must not become an uncontrolled parallel route around controls defined only for IPv4.

Storage and access upgrades

The Longhorn 1.8.2 move should be tested beyond successful pod startup. Teams need snapshot, volume-restore, node-failure, disk-reattachment and replica-load tests. Check the compatibility matrix and prepare a verified rollback before upgrading.

For external authentication, keep a protected emergency local account and audit every use. A connection test reduces configuration risk but does not replace a failure scenario for the identity provider itself.

What the announcement does not prove

The vendor announcement describes release contents, not independent performance, availability or upgrade-duration results. IPv6 support also does not establish compatibility with every network plugin and security control.

An upgrade decision should follow a staging run using the production Kubernetes version, CNI, storage type and access policy.

Practical conclusion

Botsman EE 3.4 addresses several operational concerns: IPv6, more predictable external identity setup, a Longhorn update and a fix for exposed settings.

Its business value depends on an end-to-end network, identity and persistent-data test. Individually healthy components do not guarantee resilience for the complete application path.

Source: the official Astra Group announcement dated 7 July 2026.