Minato 0.2.0 Alpha: Persistent Game Servers on Kubernetes

What's New in 0.2.0 Alpha

After months of internal dogfooding, we're excited to open the Minato alpha to the community. This release establishes the core architecture that will carry us to 1.0.

Operator + Agent SDK

The Minato Operator is a Kubernetes controller that manages GameServer custom resources. Each game type gets an Agent — a lightweight sidecar that handles game-specific logic via our Go SDK.

### Key features in this release:

• **GameServer CRD** with lifecycle management
• **GameServerSet** for grouped server management
• **Fleet** abstraction for multi-region deployments
• **Agent SDK v0.1** with signaling and state sync APIs
• **GitOps integration** via ArgoCD annotations

Why StatefulSets?

Most game server platforms use Deployments. We chose StatefulSets because:

1. **Persistent identity**: Each server keeps its name and storage across restarts
2. **Ordered operations**: Rolling updates don't kill active player sessions
3. **PVC support**: Game state and logs survive pod rescheduling

Getting Started

Deploy the operator:

kubectl apply -f https://github.com/7K-Group/minato/releases/download/v0.2.0-alpha/install.yaml

Define your first GameServer:

apiVersion: minato.7kgroup.io/v1
kind: GameServer
metadata:
  name: minecraft-01
spec:
  game: minecraft
  agentImage: ghcr.io/7k-group/minato-minecraft-agent:v0.1.0
  ports:
    - name: game
      containerPort: 25565
  storage: 10Gi

What's Next

• Matchmaking service integration
• Auto-scaling based on player queue depth
• Multi-cluster federation
• Unity and Unreal Engine SDKs

Join the Community

Star us on GitHub, join our Discord, or open an issue. We're building this in public and every contribution matters.