feat: infraestrutura Prefect 3 no cluster (servidor, workers, banco) - #137
Merged
Conversation
- Add Cloud SQL database and user for Prefect 3 (prefect3/prefect3) with auto-generated password stored in GCP Secret Manager - Add k8s/prefect3 namespace with db-service, issuer and ingress pointing to prefect3.basedosdados.org
chunksCache: 8192 MB -> 512 MB (pico real de 7d: 387Mi) resultsCache: 1024 MB -> 64 MB (uso real constante: 2Mi) Retenção de 6 meses (4320h) via compactor — PVC cresce ~10 GB/mês, estado estável estimado em ~60 GB dos 100 GB disponíveis.
💰 Infracost reportMonthly estimate increased by $0.06 📈
*Usage costs can be estimated by updating Infracost Cloud settings, see docs for other options. Estimate details |
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat: infraestrutura Prefect 3 no cluster
Contexto
Este PR adiciona toda a infraestrutura necessária para rodar o Prefect 3 no cluster Kubernetes, substituindo o Prefect 0.
A nova arquitetura separa o servidor Prefect 3 (API, UI, banco de dados) dos workers (processos que executam os flows). Os workers se conectam ao servidor via API e executam os flows dentro do cluster, com acesso às credenciais GCP necessárias para cada ambiente.
O banco de dados do Prefect 3 roda no Cloud SQL (provisionado via Terraform) e é exposto ao cluster via headless service, seguindo o mesmo padrão já usado pelo banco do backend.
Organização de arquivos
Componentes
Servidor Prefect 3
Instalado via Helm no namespace
prefect3. Exposto emprefect3.basedosdados.orgcom TLS via cert-manager.O banco de dados roda no Cloud SQL e é acessado pelo servidor via
db-service.yaml(headless service que resolve para o IP da instância Cloud SQL), sem necessidade de Cloud SQL Proxy.Workers
Dois workers instalados via Helm, cada um em seu próprio namespace:
basedosdadosprefect-workerbasedosdados-devprefect-worker-devCada worker recebe as credenciais GCP necessárias via sealed secrets montados como arquivos. O worker de produção recebe uma credencial extra para acesso ao bucket de dev (usado por flows de staging que rodam no worker de prod).
Banco de dados (Terraform)
Instância Cloud SQL PostgreSQL provisionada via Terraform, referenciada nos
variables.tfdo módulo raiz.Credenciais
Os sealed secrets de cada worker contêm:
secret-01secret-02secret-03O
secret-00do servidor contém as credenciais de conexão com o banco e a API key do Prefect 3.