How vin65/cert-secret-syncer works
• Kubernetes Cluster – Represent the cluster environment where all operations occur.
• cert-secret-syncer Controller – This is your core controller (the Go code under cmd and util) which:
– Monitors secrets with special annotations.
– Extracts certificates.
– Pushes certificates into AWS Certificate Manager.
– Pulls back the generated ARN and annotates the secret.
– Updates any Ingress resources that match provided label selectors.
• AWS Infrastructure – Represent AWS Certificate Manager (ACM) and the IAM Role (created via Terraform and integrated with EKS using IRSA) that permits the controller to perform ACM operations.
• Ingress / ALB – Everything that involves communication with Application Load Balancers where the certificate ARN is applied via annotations so that TLS termination happens correctly.
Relationships and Data Flow
• IRSA/IAM role integration providing secure credentials for cert-secret-syncer to communicate with AWS ACM.
Architectural Patterns and Design Principles
• Event-driven: The controller uses Kubernetes events to trigger certificate synchronization.
• Separation of Concerns: Highlight that the controller is separate from certificate creation (handled by cert-manager) and from the deployment configuration (given by the Helm charts).
• Infrastructure as Code: Emphasize that the project provides Helm charts (in charts) and Terraform examples (documented in the README) for managing deployments and permissions.
Technologies/Frameworks
• Go (with main command logic in cmd/main.go and utilities in util)
• Kubernetes (resource watching, Custom Resource Definitions if any, ServiceAccount with annotations)
• Helm (for packaging and deployment of the controller)
• AWS Certificate Manager and IAM (integrated via IRSA)
• Possibly Docker (docker files available for image building)