First Steps
This guide covers the fundamental steps to deploy applications on the ANDES platform, ensuring you have the environment, credentials, and basic resources required. During this process you will apply the minimum configuration, validate connectivity and permissions, and establish the foundation for publishing and operating on ANDES infrastructure.
1) IT Asset creation (Owner: Architects) Official source
The first step is to register the project in the CMDB (Configuration Management Database). The CMDB is the central database that contains detailed information about all IT components and services in the organization. In this step you must create an IT Element for the product. This registration is essential because it assigns a unique identity, enabling proper tracking and management throughout its lifecycle. It forms the basis for audits, change management, and impact analysis.
2) IT Asset import in ANDES (Owner: TLS) Enable IT Assets
Once the IT Asset has been created in the CMDB, the next step is to import it into ANDES. This ensures full visibility and centralized control, since ANDES uses CMDB information to provision and manage resources automatically.
3) Base Setup configuration (Owner: TLS)
The ANDES platform provides a Base Setup that includes replication of standard resources across the three environments (development, integration, and production). Each squad receives a set of resources managed in Google Cloud Platform (GCP) that enable secure, environment-isolated deployment:
- Standard GKE cluster (Standard mode, not Autopilot): Provides granular control over nodes and node pools, including machine types, autoscaling, taints/labels, and affinities
- Cloud Armor: Perimeter protection with WAF and DDoS mitigation
- Dedicated subnet: Network segmentation within a VPC for controlled routing
- Cloud NAT: Internet egress without exposing public IPs on nodes or pods
- KMS: Centralized key management and encryption of secrets and data at rest
This baseline establishes the operational and security foundation each team needs to continue configuring and publishing services on ANDES in a consistent, governed way.
4) GCP IAM project configuration (Owner: TLS) GCP label setup
Once the project has been provisioned, configure it by adding the appropriate labels to the project.
5) GCP project synchronization
GCP projects synchronize every 3 hours, so the project may not appear immediately in the portal after the previous step.
6) Squad configuration (Owner: Team leads) Squad Management
Once the technical foundation is in place, the next step is to configure the corresponding squad.
7) First application deployment (Owner: TLS and Developers) Bootstrap Application
The Bootstrap Application lets developers create an application with all required resources:
- Entra ID App Registration: Application registration in the active directory
- DNS: Domain name configuration
- Database instance: The process can take up to 30 minutes to complete
- Bastion: If database creation is selected, a bastion is automatically created for the new instance, enabling database connectivity. This bastion is available in the ANDES portal as a Google Compute Engine instance under VM instances