What's new on Servers.com

June 2026

Managed Kubernetes — controlled version lifecycle introduced

Managed Kubernetes clusters now follow a support lifecycle for Kubernetes versions, keeping clusters on supported and secure versions.

• each Kubernetes version now has three lifecycle dates: maintenance start, end-of-life (EOL), and automatic upgrade
• notifications appear in the portal and by email as a cluster approaches each date
• when a cluster reaches its automatic upgrade date and a safe upgrade path exists, the cluster is upgraded to a supported version, using the configured maintenance window where possible

Current version status and upgrade dates are shown in the Managed Kubernetes section of the portal.

Note: a cluster that fails auto-upgrade three times is flagged for unmanaged conversion, which starts the offboarding notice sequence.

More in version support policy

Managed Kubernetes — DNS-based high availability API

Cluster API access can now stay reachable through DNS endpoints instead of a single IP, reducing disruption during failover.

• Portal, and kubeconfig generation support public and private DNS endpoints in the form public.<zone>:6443 / private.<zone>:6443
• enabled by default for new clusters
• existing IP-based kubeconfigs remain fully compatible

Resource groups — aggregative type added for L2 Segments

L2 Segments can now be organized and access-controlled through IAM the same way other resources are.

• a resource group type — Aggregative or Resource-based — must be chosen on creation
• a default aggregative resource group is created automatically and existing L2 Segments assigned to it
• L2 Segment pages now respect IAM permissions for Hosts, Kubernetes nodes, and Direct Connect

L7 Load Balancer — GRPC and HTTP/2 combination restricted

New load balancers can no longer be created with a protocol combination known to cause issues.

• creating or editing an L7 load balancer is now blocked when GRPC/GRPCs protocols are combined with HTTP/2 enabled

Note: existing load balancers already using this combination are unaffected and continue to work.

AI Compute — access request form enabled

Customers interested in AI Compute can now request access directly from the Customer Portal instead of contacting sales separately.

Dedicated servers — OS reinstall via Terraform

Dedicated server reinstalls can now be scripted as part of infrastructure-as-code workflows.

Reinstalling the operating system on dedicated servers is now supported through the Terraform provider.

May 2026

GPG key management — governed by IAM permissions

Access to GPG key creation and deletion in the Portal is now controlled by IAM permissions, consistent with other key management operations.

April 2026

IAM permission policies — export and import across accounts

Permission policies can be exported to JSON and imported into other accounts, making it easier to maintain consistent access configurations across a multi-account organisation. More in IAM documentation.

SSL certificate renewal errors — actionable messages returned

An issue that caused SSL certificate renewal failures to return unclear error responses has been resolved; the API now returns specific, actionable messages.

Remote Block Storage — available in beta

Scalable block storage can be added to servers without replacing or installing local disks. More in Remote Block Storage.

• create, attach, resize, disable, and delete volumes via Customer Portal, Public API, Terraform, and Kubernetes (RBS CSI driver)
• currently available in AMS7; volumes can be used from other locations, but IOPS and bandwidth depend on network latency
• volumes can be resized and temporarily disabled without deletion

Note: this is a beta release. For best performance, use RBS with servers in the same datacenter (AMS7).

Managed Kubernetes — pod limit increased to 250 per node

New clusters support up to 250 pods per worker node, up from 110. The Pod CIDR per node has been widened to /23 to accommodate the higher pod count.

Note: applies to new clusters only. Existing clusters and nodes added to existing clusters are unaffected. No action required.

iPXE boot — available for EBM servers

EBM servers can boot from a custom iPXE script over the network on every start, without going through the standard OS installer. More in Public API.

• two modes available: public iPXE boot (via public network interface) and private iPXE boot (via private interface)
• script URL and optional user_data string configurable without reprovisioning
• MAC addresses and DNS server addresses automatically injected as variables before the script runs
• activate at order time via the features field, or on an existing server via /features/public_ipxe_boot/activate or /features/private_ipxe_boot/activate
• to update the script on a running server: deactivate, update ipxe_config via PUT, reactivate, and reboot

March 2026

IAM — beta release with updated Team and Permission Policy management

Identity and Access Management is now in beta, with documentation and UX improvements that make it easier to configure access control for account members and resource groups. More in IAM documentation.

Kubernetes Node Groups — available

Worker nodes can be grouped within a cluster to separate workloads logically and apply consistent scheduling labels across a group. More in Node Groups.

• create, rename, and delete node groups from the Portal or via /v1/kubernetes_node_groups PAPI endpoint
• nodes can be assigned to a group at add time, or moved later individually or in bulk
• existing clusters have been automatically included into a default node group

Kubernetes worker nodes — addable in nearby locations

When the cluster's primary location has no available bare-metal capacity, worker nodes can be added in a nearby location with the same location prefix (e.g. AMS2 or AMS3 for a cluster in AMS1). More in Add a worker node.

• cross-location connectivity handled automatically over GPN; no manual network configuration required
• Portal shows a Location selector when adding a node and a Location column in the nodes list

February 2026

Pre-paid service billing — ECB exchange rates applied

Invoices and charges for pre-paid services are calculated using up-to-date currency conversions from European Central Bank rather than a fixed monthly rate.

Account settings page — redesigned, 2FA guidance improved

The account settings page has an improved layout and 2FA enforcement guidance on what to do next. More in Enforce 2FA.

• account settings page layout redesigned for easier navigation
• 2FA setup flow includes better UX guidance when 2FA is enforced at the organisation level

IAM permissions — extended to Direct Connect and Portal dashboard widgets

Identity and Access Management permissions have been extended:

• all Direct Connect operations are now subject to IAM permission checks
• Portal dashboard widgets are hidden for users who lack the required permissions

Contact-level permissions — managed independently from account-level administrative scope

Account administrators have finer-grained control over what contacts can do without affecting account-wide settings.

Kubernetes minor version upgrades — self-service

Kubernetes clusters can be upgraded to a new minor version directly from the Customer Portal, with full control over how worker nodes are upgraded. More in Kubernetes upgrades.

• supported upgrade paths: versions 1.27 through 1.35
• configurable upgrade strategy per node batch: drain with halt, drain with skip, drain with force, or force
• configurable batch size and delay between batches
• per-node upgrade status visible in real time during the upgrade
• individual failed nodes can be retried
• per-node report available for download after upgrade

Note: clusters cannot be downgraded. Upgrades proceed one minor version at a time.

Scalable Bare Metal — available

Physical dedicated servers are available on an hourly, no-commitment basis in four predefined configurations. More in Scalable Bare Metal.

• available flavors range from 8-core entry to dual-socket 56-core with NVMe storage and up to 10 Gbps networking
• available in AMS7, WAS4, DFW5, and SJC2;
• average provisioning time ~15 minutes;
• billing is hourly; public outbound traffic charged per GB; private traffic is free
• manageable via Customer Portal, /v1/hosts/sbm_servers PAPI endpoint, and Terraform