|
| 1 | +# Anthos |
| 2 | + |
| 3 | +## Core Concepts |
| 4 | + |
| 5 | +Anthos is a hybrid and multi-cloud application platform built on Kubernetes. Enables consistent development and operations across on-premises, GCP, AWS, and Azure. |
| 6 | + |
| 7 | +**Key Principle**: Write once, run anywhere; consistent K8s experience across environments. |
| 8 | + |
| 9 | +## Anthos Components |
| 10 | + |
| 11 | +| Component | Purpose | Key Feature | |
| 12 | +|-----------|---------|-------------| |
| 13 | +| **GKE/Anthos clusters** | Kubernetes clusters | Anywhere (on-prem, clouds) | |
| 14 | +| **Anthos Config Management** | Policy and config | GitOps, multi-cluster sync | |
| 15 | +| **Anthos Service Mesh** | Service-to-service communication | Traffic management, security | |
| 16 | +| **Cloud Run for Anthos** | Serverless on K8s | Knative-based | |
| 17 | +| **Anthos on VMware/Bare Metal** | On-premises K8s | Run on existing infrastructure | |
| 18 | + |
| 19 | +## When to Use Anthos |
| 20 | + |
| 21 | +### ✅ Use Anthos When |
| 22 | + |
| 23 | +- Hybrid cloud strategy (on-prem + cloud) |
| 24 | +- Multi-cloud deployment needed |
| 25 | +- Existing on-premises infrastructure |
| 26 | +- Kubernetes standardization across environments |
| 27 | +- Modernizing VMs to containers gradually |
| 28 | +- Need consistent policy enforcement |
| 29 | +- Service mesh requirements |
| 30 | + |
| 31 | +### ❌ Don't Use Anthos When |
| 32 | + |
| 33 | +- GCP-only deployment → GKE sufficient |
| 34 | +- Simple applications → Cloud Run |
| 35 | +- No Kubernetes needed → App Engine, Cloud Functions |
| 36 | +- Not ready for containerization → Compute Engine |
| 37 | +- Budget-constrained (Anthos has licensing cost) |
| 38 | + |
| 39 | +## Deployment Options |
| 40 | + |
| 41 | +### GKE (Google Cloud) |
| 42 | + |
| 43 | +**Benefits**: Fully managed, latest features, easiest |
| 44 | + |
| 45 | +**Use case**: Cloud-native applications on GCP |
| 46 | + |
| 47 | +### Anthos on VMware |
| 48 | + |
| 49 | +**Architecture**: Run GKE on VMware vSphere |
| 50 | + |
| 51 | +**Benefits**: |
| 52 | + |
| 53 | +- Use existing VMware investment |
| 54 | +- Keep data on-premises (compliance) |
| 55 | +- Hybrid cloud connectivity |
| 56 | + |
| 57 | +**Requirements**: vSphere 6.7+, sufficient resources |
| 58 | + |
| 59 | +### Anthos on Bare Metal |
| 60 | + |
| 61 | +**Architecture**: Run GKE directly on physical servers |
| 62 | + |
| 63 | +**Benefits**: |
| 64 | + |
| 65 | +- No hypervisor overhead |
| 66 | +- Edge computing scenarios |
| 67 | +- Cost savings (no VMware licenses) |
| 68 | + |
| 69 | +**Requirements**: Qualified hardware, network configuration |
| 70 | + |
| 71 | +### Anthos on AWS/Azure |
| 72 | + |
| 73 | +**Purpose**: Consistent K8s across clouds |
| 74 | + |
| 75 | +**Benefits**: Multi-cloud strategy, avoid lock-in |
| 76 | + |
| 77 | +**Limitations**: Additional complexity, cost |
| 78 | + |
| 79 | +## Anthos Config Management (ACM) |
| 80 | + |
| 81 | +### Purpose |
| 82 | + |
| 83 | +Centralized configuration and policy management for multiple clusters using GitOps. |
| 84 | + |
| 85 | +### Key Features |
| 86 | + |
| 87 | +**Policy Controller**: |
| 88 | + |
| 89 | +- Enforce policies across clusters |
| 90 | +- Based on Open Policy Agent (OPA) |
| 91 | +- Examples: Require labels, restrict registries, enforce resource limits |
| 92 | + |
| 93 | +**Config Sync**: |
| 94 | + |
| 95 | +- Sync configs from Git to clusters |
| 96 | +- Single source of truth |
| 97 | +- Automatic reconciliation |
| 98 | +- Namespace and cluster-scoped configs |
| 99 | + |
| 100 | +### GitOps Workflow |
| 101 | + |
| 102 | +``` |
| 103 | +Git Repository (configs) → Config Sync → Multiple clusters apply configs |
| 104 | +``` |
| 105 | + |
| 106 | +**Benefits**: Version control, audit trail, declarative, automated |
| 107 | + |
| 108 | +### Common Policies |
| 109 | + |
| 110 | +- Require specific labels |
| 111 | +- Enforce namespace quotas |
| 112 | +- Restrict container registries |
| 113 | +- Require pod security policies |
| 114 | +- Enforce naming conventions |
| 115 | + |
| 116 | +## Anthos Service Mesh (ASM) |
| 117 | + |
| 118 | +### Purpose |
| 119 | + |
| 120 | +Managed service mesh for observability, security, and traffic management. |
| 121 | + |
| 122 | +### Architecture |
| 123 | + |
| 124 | +Based on Istio, fully managed by Google |
| 125 | + |
| 126 | +**Components**: |
| 127 | + |
| 128 | +- **Control Plane**: Managed by Google |
| 129 | +- **Data Plane**: Envoy sidecars in pods |
| 130 | + |
| 131 | +### Features |
| 132 | + |
| 133 | +**Traffic Management**: |
| 134 | + |
| 135 | +- Load balancing |
| 136 | +- Circuit breaking |
| 137 | +- Retries and timeouts |
| 138 | +- Canary deployments |
| 139 | +- Traffic splitting |
| 140 | + |
| 141 | +**Security**: |
| 142 | + |
| 143 | +- mTLS between services (automatic) |
| 144 | +- Authorization policies |
| 145 | +- Service-to-service auth |
| 146 | +- Certificate management |
| 147 | + |
| 148 | +**Observability**: |
| 149 | + |
| 150 | +- Service topology visualization |
| 151 | +- Distributed tracing |
| 152 | +- Metrics and logs |
| 153 | +- Service-level objectives (SLOs) |
| 154 | + |
| 155 | +### Use Cases |
| 156 | + |
| 157 | +- Microservices communication |
| 158 | +- Zero-trust security |
| 159 | +- Canary deployments |
| 160 | +- Service observability |
| 161 | +- Multi-cluster service mesh |
| 162 | + |
| 163 | +## Cloud Run for Anthos |
| 164 | + |
| 165 | +**Purpose**: Serverless containers on your GKE clusters |
| 166 | + |
| 167 | +**Benefits**: |
| 168 | + |
| 169 | +- Knative-based |
| 170 | +- Auto-scaling (including to zero) |
| 171 | +- Simplified deployment |
| 172 | +- Use existing GKE clusters |
| 173 | + |
| 174 | +**vs Cloud Run**: Same developer experience, runs on your infrastructure |
| 175 | + |
| 176 | +**Use case**: Serverless on-premises or in specific clusters |
| 177 | + |
| 178 | +## Architecture Patterns |
| 179 | + |
| 180 | +### Hybrid Application |
| 181 | + |
| 182 | +``` |
| 183 | +On-prem (Anthos on VMware): Legacy systems + databases |
| 184 | +GCP (GKE): Modern microservices |
| 185 | +Connected via: VPN/Interconnect + Anthos Service Mesh |
| 186 | +``` |
| 187 | + |
| 188 | +**Benefits**: Gradual migration, keep sensitive data on-prem |
| 189 | + |
| 190 | +### Multi-Region HA |
| 191 | + |
| 192 | +``` |
| 193 | +GKE Cluster (us-central1) |
| 194 | +GKE Cluster (europe-west1) |
| 195 | +GKE Cluster (asia-east1) |
| 196 | +Managed by: Anthos Config Management |
| 197 | +Service Mesh: Cross-cluster communication |
| 198 | +``` |
| 199 | + |
| 200 | +### Edge Computing |
| 201 | + |
| 202 | +``` |
| 203 | +Anthos on Bare Metal (retail stores/factories) |
| 204 | +Central GKE (cloud) |
| 205 | +Sync: Anthos Config Management |
| 206 | +``` |
| 207 | + |
| 208 | +**Use case**: Low latency, local data processing, offline capability |
| 209 | + |
| 210 | +### Multi-Cloud |
| 211 | + |
| 212 | +``` |
| 213 | +GKE (GCP) + EKS via Anthos (AWS) + AKS via Anthos (Azure) |
| 214 | +Unified: Config Management + Service Mesh |
| 215 | +``` |
| 216 | + |
| 217 | +**Benefits**: Avoid vendor lock-in, geographic coverage, redundancy |
| 218 | + |
| 219 | +## Migrate to Containers (M4C) |
| 220 | + |
| 221 | +**Purpose**: Migrate VMs to containers running on GKE/Anthos |
| 222 | + |
| 223 | +**Process**: |
| 224 | + |
| 225 | +1. Discover and assess VMs |
| 226 | +2. Generate migration plan |
| 227 | +3. Convert VM to container |
| 228 | +4. Deploy to GKE/Anthos |
| 229 | +5. Optimize containerized workload |
| 230 | + |
| 231 | +**Use case**: Modernize legacy applications, VM to container migration |
| 232 | + |
| 233 | +## Security Features |
| 234 | + |
| 235 | +### Binary Authorization |
| 236 | + |
| 237 | +**Purpose**: Enforce only trusted container images deployed |
| 238 | + |
| 239 | +**How**: Cryptographic signatures on images, attestation checks |
| 240 | + |
| 241 | +**Use case**: Compliance, supply chain security |
| 242 | + |
| 243 | +### Policy Controller |
| 244 | + |
| 245 | +**Purpose**: Enforce organizational policies on clusters |
| 246 | + |
| 247 | +**Examples**: |
| 248 | + |
| 249 | +- Only approved container registries |
| 250 | +- Required labels on resources |
| 251 | +- Prohibited capabilities |
| 252 | +- Resource quotas |
| 253 | + |
| 254 | +### Service Mesh Security |
| 255 | + |
| 256 | +**mTLS**: Automatic encryption between services |
| 257 | +**Authorization**: Fine-grained access control |
| 258 | +**Certificate Management**: Automated, no manual cert handling |
| 259 | + |
| 260 | +### Workload Identity |
| 261 | + |
| 262 | +**Purpose**: Kubernetes service accounts → Google service accounts |
| 263 | + |
| 264 | +**Benefits**: Secure access to GCP services, no keys in pods |
| 265 | + |
| 266 | +## Cost Considerations |
| 267 | + |
| 268 | +**Anthos Licensing**: |
| 269 | + |
| 270 | +- Per-vCPU pricing for on-premises |
| 271 | +- Included with GKE on GCP |
| 272 | +- Additional cost for multi-cloud |
| 273 | + |
| 274 | +**Infrastructure Costs**: |
| 275 | + |
| 276 | +- GKE: Standard GCP compute pricing |
| 277 | +- On-premises: Your hardware + VMware licenses (if applicable) |
| 278 | +- Network: Interconnect, VPN, egress |
| 279 | + |
| 280 | +**Optimization**: |
| 281 | + |
| 282 | +- Right-size clusters |
| 283 | +- Use Autopilot GKE (managed) |
| 284 | +- Optimize workload placement |
| 285 | +- Monitor with recommendations |
| 286 | + |
| 287 | +## Monitoring and Operations |
| 288 | + |
| 289 | +### Cloud Monitoring |
| 290 | + |
| 291 | +- Cluster metrics |
| 292 | +- Application metrics |
| 293 | +- Service mesh metrics |
| 294 | +- Custom metrics |
| 295 | + |
| 296 | +### Cloud Logging |
| 297 | + |
| 298 | +- Cluster logs |
| 299 | +- Application logs |
| 300 | +- Audit logs |
| 301 | +- Centralized logging |
| 302 | + |
| 303 | +### Service Mesh Observability |
| 304 | + |
| 305 | +- Service topology |
| 306 | +- Request rates |
| 307 | +- Latencies |
| 308 | +- Error rates |
| 309 | +- SLI/SLO tracking |
| 310 | + |
| 311 | +## Exam Focus |
| 312 | + |
| 313 | +### Core Concepts |
| 314 | + |
| 315 | +- What is Anthos (hybrid/multi-cloud K8s platform) |
| 316 | +- Components (GKE, Config Mgmt, Service Mesh) |
| 317 | +- When to use vs GKE alone |
| 318 | +- Deployment options (VMware, bare metal, clouds) |
| 319 | + |
| 320 | +### Use Cases |
| 321 | + |
| 322 | +- Hybrid cloud (on-prem + cloud) |
| 323 | +- Multi-cloud strategy |
| 324 | +- Edge computing |
| 325 | +- Gradual VM-to-container migration |
| 326 | + |
| 327 | +### Architecture |
| 328 | + |
| 329 | +- Hybrid application design |
| 330 | +- Multi-cluster management |
| 331 | +- Service mesh benefits |
| 332 | +- GitOps with Config Management |
| 333 | + |
| 334 | +### Config Management |
| 335 | + |
| 336 | +- Policy enforcement |
| 337 | +- Config sync |
| 338 | +- GitOps workflow |
| 339 | +- Multi-cluster consistency |
| 340 | + |
| 341 | +### Service Mesh |
| 342 | + |
| 343 | +- mTLS between services |
| 344 | +- Traffic management |
| 345 | +- Observability |
| 346 | +- Security policies |
| 347 | + |
| 348 | +### Security |
| 349 | + |
| 350 | +- Binary Authorization |
| 351 | +- Policy Controller |
| 352 | +- Workload Identity |
| 353 | +- Zero-trust networking |
| 354 | + |
| 355 | +### Migration |
| 356 | + |
| 357 | +- Migrate to Containers (M4C) |
| 358 | +- VM to container modernization |
| 359 | +- Gradual migration strategy |
0 commit comments