Skip to content

fix(ci): raise local infrastructure Flux timeout to 20m for vault-config bootstrap #1648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
devantler wants to merge 1 commit into from
+18 −0
Closed

fix(ci): raise local infrastructure Flux timeout to 20m for vault-config bootstrap #1648

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions k8s/clusters/local/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,24 @@ patches:
namespace: flux-system
spec:
timeout: 12m
# The vault-config Job co-located in the infrastructure layer (see
# bases/infrastructure/vault-config/job.yaml) bootstraps OpenBao —
# KV engine, Kubernetes auth, policies, roles — and is depended on
# intra-Kustomization by the openbao ClusterSecretStore consumers
# (ExternalSecrets, vault-seed PushSecrets). On cold Docker CI runners
# the Job legitimately takes longer than the 3m base health-check
# budget, which caused system-test flakes (see PR #1636 run
# 26603473269: `[Job/openbao/vault-config status: 'InProgress']
# (HealthCheckFailed)`). The Job's own activeDeadlineSeconds is 3600s.
# 20m mirrors the prod patch value for the same Kustomization.
- patch: |
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: infrastructure
namespace: flux-system
spec:
timeout: 20m

replacements:
# Point apps / infrastructure / infrastructure-controllers Flux Kustomizations
Expand Down
Loading