Infrastructure Naming Conventions
Overview
This document defines the standardized naming conventions for all infrastructure resources across the MCP Server LangGraph project. All resources follow the pattern:{environment}-mcp-server-langgraph-{resource-type}.
Last Updated: 2025-11-04
Status: ✅ Standardized across GCP, AWS, and Azure
Core Naming Pattern
Standard Format
⚠️ Dual-Prefix Strategy for GCP
Due to GCP character limits on certain resources, we use a dual-prefix approach:-
Full Prefix (
{env}-mcp-server-langgraph): For resources without length limits- GKE Clusters, Kubernetes Namespaces, Deployments, Services
-
Short Prefix (
{env}-mcp-slg): For resources with GCP character limits- VPC (20 char max), Cloud SQL, Memorystore Redis, Service Accounts (30 char max)
Environments
Resource Types
Platform-Specific Naming
Google Cloud Platform (GKE)
Cluster Names
Namespaces
Deployments (with Kustomize namePrefix)
Services
Other GCP Resources (Using Short Prefix)
Note: Short prefix =
{env}-mcp-slg (e.g., preview-mcp-slg, production-mcp-slg, dev-mcp-slg)
Amazon Web Services (EKS)
Cluster Names
Namespaces
Other AWS Resources
Microsoft Azure (AKS)
Cluster Names
Namespaces
Other Azure Resources
Kubernetes Resources
Kustomize Configuration
Base Resources
Environment Overlays
Generated Resource Names
WithnamePrefix applied:
Container Images
Repository Naming
GitHub Container Registry (GHCR)
Google Artifact Registry (GAR)
AWS ECR
Image Tags
GitHub Actions Variables
Cluster Variables
Namespace Variables
Deployment Names
Terraform Locals
Name Prefix Pattern
Scripts and CLI Tools
Environment Variables
Legacy Naming (Deprecated)
Old Patterns (DO NOT USE)
Migration Status
Naming Rules and Guidelines
Rules
- Environment-First: Always start with the environment name (
dev,staging,production) - Consistent Separators: Use hyphens (
-) for all multi-word names - Lowercase Only: All infrastructure names must be lowercase
- No Underscores: Use hyphens instead of underscores (except in variable names)
- Platform Suffix: Add platform suffix (
-gke,-eks,-aks) for cluster names - No Platform in Namespaces: Namespaces are platform-agnostic
Exceptions
- Artifact Registry Repos: Use
mcp-{env}pattern for simplicity - Legacy Service Accounts: Some SA names may retain
mcp-{env}-*pattern - Generic Platform Overlays: AWS/Azure Kustomize overlays use generic
mcp-server-langgraphnamespace
Validation
Automated Checks
Add to.github/workflows/validate.yaml:
Manual Verification
References
- Terraform:
terraform/environments/{platform}-{env}/main.tf - Kustomization:
deployments/overlays/{platform}/kustomization.yaml - Workflows:
.github/workflows/deploy-{env}-{platform}.yaml - Scripts:
scripts/{platform}/*.sh - Secrets:
SECRETS.md
Support
For questions or clarifications:- Review this document first
- Check implementation in Terraform/Kustomization files
- Consult team leads for approval before deviating