Deploying GC2 with Precreated IAM Roles
A step-by-step technical walkthrough for deploying Nutanix Government Cloud Clusters in accounts where the operator can't touch IAM: precreate every role first, deploy last.
Architectures, traffic flows, and field notes on Nutanix NC2, Kubernetes, and running enterprise infrastructure in the public cloud.
A step-by-step technical walkthrough for deploying Nutanix Government Cloud Clusters in accounts where the operator can't touch IAM: precreate every role first, deploy last.
Comparing pocket-tts against voicebox's chatterbox backend for cloned-voice narration, on the same laptop CPU, same reference clip, same test sentences.
Nutanix Government Cloud Clusters used to require the person deploying to hold full IAM rights. GC2 1.2 splits that into two roles, and it's a bigger deal for teams than it sounds.
Default Claude Code leaves the token meter running hard. Four skills cut the bill from four different angles: the words it writes, the code it builds, the motion it wastes, and the context it drags around.
The GPU gets all the hype, but the model runs on a GPU while the agent lives on a VM. Long-running agentic work is a stateful, always-on workload, and the hard parts - uptime, state, rollback, secure multi-tenancy, blast-radius containment - are classic virtualization problems Nutanix already solved.
Every packet in and out of your NC2 user VMs crosses the Flow Gateway, so for real workloads you run a scaled-out set. There are two ways to spread traffic across them. One bills you by the hour for a Route Server and a pair of BGP VMs. The other is an internal load balancer you already understand - and NC2 builds it for you.