# June 2026 (/docs/news/2026/news-06-26)



<NewsSection tags={['managed_kubernetes']}>
  ### 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](https://www.servers.com/docs/managed-kubernetes/version-support-policy/)

  <Badge type="new" />

  <Tag>
    Managed Kubernetes
  </Tag>
</NewsSection>

<NewsSection tags={['managed_kubernetes']}>
  ### 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

  <Badge type="new" />

  <Tag>
    Managed Kubernetes
  </Tag>
</NewsSection>

<NewsSection tags={['l2_segments', 'platform']}>
  ### 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

  <Badge type="new" />

  <Tag>
    L2 Segments
  </Tag>

  <Tag>
    Platform
  </Tag>
</NewsSection>

<NewsSection tags={['load_balancer']}>
  ### 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.*

  <Badge type="improved" />

  <Tag>
    Load Balancer
  </Tag>
</NewsSection>

<NewsSection tags={['platform']}>
  ### AI Compute — access request form enabled

  Customers interested in AI Compute can now request access directly from the [Customer Portal](https://portal.servers.com/ai-compute/welcome) instead of contacting sales separately.

  <Badge type="new" />

  <Tag>
    Platform
  </Tag>
</NewsSection>

<NewsSection tags={['platform']}>
  ### 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](https://registry.terraform.io/providers/serverscom/serverscom/latest/docs/resources/dedicated_server).

  <Badge type="new" />

  <Tag>
    Platform
  </Tag>
</NewsSection>