Harbor and Gitea Multi-AZ Active-Active Migration: Token Key Sharing and Traffic Strategy

·2026.11.18 15:28

Key point

High availability was achieved through token signing key sharing and zone-aware traffic configuration.

1 / 2

Details

  • Migrated Harbor and Gitea to a multi-AZ Active-Active architecture, resolving authentication and storage issues
  • Shared Harbor token signing keys in PKCS#1 format to prevent 401 errors across AZs
  • Handled Gitea OIDC login sessions via sticky sessions or shared storage, and separated file volumes per instance to avoid Multi-Attach
  • Configured preferLocal to prioritize the local AZ by default, with automatic failover upon health check failure
  • Executed a zero-downtime migration for running services by splitting backendRef into two stages for cutover
  • Vault and ArgoCD achieved HA solely through pod distribution due to state replication or stateless characteristics, requiring no separate state synchronization

This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.

Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.