Skip to content

feat(azure): Add Azure Container Instance module for DataHub Remote Executor#41

Open
acrylJonny wants to merge 2 commits intomainfrom
remote-executor-aci
Open

feat(azure): Add Azure Container Instance module for DataHub Remote Executor#41
acrylJonny wants to merge 2 commits intomainfrom
remote-executor-aci

Conversation

@acrylJonny
Copy link

Summary

This PR adds a new Terraform module for deploying the DataHub Remote Ingestion Executor to Azure Container Instances (ACI), providing full feature parity with the existing ECS and Helm chart deployments.

Features

  • Full DataHub Configuration: Executor pool ID, worker counts, polling intervals
  • Secret Management: Multiple approaches including secure environment variables, secret volumes, and Azure Key Vault integration
  • Networking: Support for public, private, or no IP addressing
  • Azure Integration: Managed identities, Log Analytics, Azure Files volumes
  • Health Checks: Configurable readiness and liveness probes
  • Registry Support: Uses Docker registry (docker.datahub.com/re/datahub-executor)

…xecutor

This module enables deployment of the DataHub Remote Ingestion Executor to Azure Container Instances (ACI), providing feature parity with existing ECS and Helm deployments.

Key Features:
- Full DataHub executor configuration (pool ID, workers, polling intervals)
- Multiple secret management options (environment variables, secret volumes, Key Vault)
- Azure networking support (public, private, or none IP addressing)
- Managed identity integration
- Azure Files volume mounting
- Health probes (readiness and liveness)
- Log Analytics integration
- Comprehensive documentation with examples

Tested and validated:
- Successfully deployed to Azure Container Instance
- Connected to test-environment.acryl.io
- Verified executor pool registration and task processing
- Uses Docker registry (docker.datahub.com/re/datahub-executor)

Module structure follows ECS module conventions with simplified documentation approach.
Terraform modules should not commit lock files as they are meant to be resolved by the consumer of the module.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant