Hyperstack Weekly Rundown 47

Hyperstack Monthly Update

March brought a range of updates to the Hyperstack platform, with a focus on improving how you interact with your infrastructure. We also released exciting tutorials on Hyperstack MCP, OpenClaw and NemoClaw following its introduction at the NVIDIA GTC 2026.

Scroll down to explore the highlights.

New on Hyperstack

Here's what we released on Hyperstack in March:

Hyperstack MCP Server

We introduced the Hyperstack MCP (Model Context Protocol) Server, a new interface layer that allows you to manage infrastructure using natural language.

Instead of relying on manual API calls or navigating multiple dashboards, the MCP Server translates plain English instructions into secure and structured API operations. This makes common tasks like provisioning VMs, managing resources or updating configurations faster and more intuitive.

The MCP Server is compatible with MCP-enabled clients such as Claude Desktop and Open WebUI. This lets you integrate infrastructure control directly into the tools you already use.

• No need to write or manage raw API calls
• Faster execution of routine infrastructure tasks
• Reduced friction in developer workflows

Node Group Firewall Management for Clusters

Firewall rules can now be defined and managed at the node group level within Kubernetes clusters. These rules can be configured directly from the console after cluster deployment and are automatically applied across all worker nodes in the selected node group.

Node Group Firewall API Support

Firewall management for node groups is now fully supported via API using the firewall_ids field. This capability is available across the following endpoints:

• Create Cluster: Apply firewall rules during cluster creation.
• Create Node Group: Apply firewall rules when adding node groups.
• Update Node Group: Update firewall rules for existing node groups.

Across all cluster-related API responses that include the node_groups object, it will now return associated firewall details for each node group.

Latest Fixes and Improvements

We also made some improvements on Hyperstack to make your experience even better:

Kubernetes Cluster Deployment Defaults

The cluster deployment experience has been improved by automatically selecting the Kubernetes version and setting Full Deployment Mode as the default option.

User Role Management Improvements

The Create and Edit User Role experience has been enhanced with:

• A new resource-based permission filter
• Clear visibility of permissions by resource group with selection counts
• Reduced horizontal scrolling and improved layout for better usability

Improved Resource Availability Error Messaging

VM and Kubernetes cluster creation failures due to temporary capacity shortages now display a clearer message, indicating resource unavailability and suggesting a retry.

VM Hibernation Request Handling Improvements

Improved lifecycle handling ensures instance states remain consistent during operations like hibernation, preventing duplicate requests while an operation is already in progress.

Firewall Attachment Improvements

Enhanced reliability and usability when attaching virtual machines to firewalls, with more consistent handling of VM states and firewall updates.

New on the Blog

---

NVIDIA GTC 2026: Conversations on Secure AI Infrastructure

Our team attended the NVIDIA GTC 2026 in March and the conversations we had there reflected something a lot of teams are thinking about right now: how to build infrastructure for production AI the right way.

We had discussions around our Secure Private Cloud and why isolation, compliance and control need to be built in from day one rather than added on later. If you're deploying AI that needs dedicated infrastructure with full visibility and governance, book a meeting with the Hyperstack team:

Your Ideas Power Hyperstack

You know your workflow better than anyone. If there’s anything you wish Hyperstack did differently or better, now’s your chance to tell us.

Maybe it’s a feature you’ve been thinking about, a tool that could speed up your workflow, or a simple improvement that would make your project easier. Whatever it is, we’re listening.

Share Feature Request →

---

 

For any questions or suggestions, feel free to reach out at support@hyperstack.cloud. Stay tuned for even more updates and exciting tools next month.

New on Hyperstack

Check out what we released on Hyperstack this week:

Hyperstack MCP Server

We’re excited to introduce the Hyperstack MCP (Model Context Protocol) Server. It is a new way to manage your infrastructure using natural language. With MCP support, users can interact with their cloud resources using natural language through compatible AI clients like Claude Desktop and Open WebUI.

The MCP Server translates plain-English instructions into secure, authenticated Hyperstack API actions. This means you can create, manage and monitor infrastructure without manually writing API calls.

Once connected, you can perform tasks such as:

• Creating and managing Virtual Machines
• Provisioning and scaling Kubernetes clusters
• Creating and attaching storage volumes
• Retrieving billing and usage information
• Managing environments
• Executing multi-step infrastructure workflows

New on our Blog

That's it for this week's Hyperstack Rundown! Stay tuned for more updates next week and subscribe to our newsletter below for exclusive AI and GPU insights delivered to your inbox!

Missed the Previous Editions? 

Catch up on everything you need to know from Hyperstack updates below:

👉 Hyperstack February Update

Hyperstack Monthly Update

It’s time for our February monthly update.

February at Hyperstack was focused on making the platform more resilient and predictable. We introduced better safeguards for Kubernetes environments, improved VM deployment reliability and enhanced networking defaults.

Scroll down to see what we shipped this month!

What’s New on Hyperstack

Here's what we released on Hyperstack in February:

Firewall Warnings for Kubernetes VMs

We’ve added a warning banner to the Firewalls tab for VMs in a Kubernetes cluster. This banner alerts users before making firewall configuration changes that could disrupt:

• Cluster networking
• Reconciliation processes

Image-Flavour Compatibility Support

Hyperstack now supports detecting compatibility between selected images and VM flavours. While no images currently define restrictions, this enables:

• Future warnings for suboptimal image
• Restrictions on incompatible configurations

Latest Fixes and Improvements

• Security Enhancements: Platform security has been further strengthened with internal improvements that increase protection and provide safer, more reliable system interactions for users and their workloads.
• Improved Usability and Error Messaging: User experience has been improved with clearer error messages and more intuitive system feedback, making it easier to understand issues and resolve them quickly.
• New “No-Reboot” Flavour Label: Applicable flavours now include a “no-reboot” label, helping users easily identify configurations that support operations without requiring instance reboots—reducing downtime and maintaining workload continuity. 
• Reliable VM Creation with Bootable Volumes via API: VM creation using the Create Virtual Machines API with create_bootable_volume = true now waits for the volume to become available before proceeding, improving provisioning reliability.
• Firewall Management Fixes: Resolved issues with firewall assignment and detachment workflows. The VM list in the firewall assignment modal now correctly shows only VMs in the same environment as the selected firewall, and the “Save changes” button now functions as expected when removing all firewall attachments from a VM.
• Improved Redirect After Session Expiry: Users are now correctly returned to the page they were on after signing in again, even if their access token was missing or had expired during refresh.
• Fixed TLS SAN Mismatch in Standard Kubernetes Deployments: The public IP address of the master node serving as both bastion and API endpoint (in Standard configuration deployments) is now included in the Kubernetes API server certificate’s Subject Alternative Names (SANs), resolving TLS handshake failures caused by hostname mismatches.
• New Default Networking Mode for Kubernetes Clusters: New Kubernetes clusters now use VXLAN encapsulation (UDP port 4789) for pod networking instead of IPIP, allowing firewall configuration without disrupting connectivity. Existing clusters remain on IPIP.
• Environment VM Limit Notification: Users are now notified during VM or cluster deployment if the selected environment has reached its maximum VM capacity, with guidance to deploy in a different environment.

New on the Blog