fix: [alert] KubeJobFailed (openbao) (#510) #511
@@ -14,7 +14,9 @@
|
||||
# immediately:
|
||||
# kubectl -n openbao create job --from=cronjob/claude-oauth-secret-sync claude-oauth-sync-now
|
||||
#
|
||||
# woodpecker is reached in-cluster at woodpecker.apps.svc:8000. Needs the netpol
|
||||
# woodpecker is reached in-cluster at woodpecker.woodpecker.svc:8000 (it moved
|
||||
# out of `apps` in the namespace migration — see
|
||||
# kubernetes/apps/woodpecker/MIGRATION-namespace.md). Needs the netpol
|
||||
# halves woodpecker-allow-rotators (apps/*) + rotator-claude-oauth-egress
|
||||
# (openbao-ns.yaml). OpenBao policy/role rotator-claude-oauth + the bootstraps
|
||||
# (woodpecker-bot token, the seeded OAuth value) are provisioned by hand — see
|
||||
@@ -89,7 +91,7 @@ spec:
|
||||
- name: BAO_FIELD
|
||||
value: setup-token
|
||||
- name: WOODPECKER_URL
|
||||
value: http://woodpecker.apps.svc.cluster.local:8000
|
||||
value: http://woodpecker.woodpecker.svc.cluster.local:8000
|
||||
- name: WOODPECKER_ORG
|
||||
value: k.renner
|
||||
- name: WOODPECKER_SECRET_NAME
|
||||
|
||||
@@ -25,7 +25,8 @@
|
||||
# but a failed sync should be fixed before the next run rather than left.
|
||||
#
|
||||
# gitea is reached in-cluster at gitea.apps.svc:3000, woodpecker at
|
||||
# woodpecker.apps.svc:8000 (both hairpin off the ingress LB from a pod). Needs
|
||||
# woodpecker.woodpecker.svc:8000 (it moved out of `apps` in the namespace
|
||||
# migration — see kubernetes/apps/woodpecker/MIGRATION-namespace.md). Needs
|
||||
# the netpol halves: gitea-allow-review-bot-rotator + woodpecker-allow-rotators
|
||||
# (apps/*) and rotator-review-bot-egress (openbao-ns.yaml).
|
||||
#
|
||||
@@ -147,7 +148,7 @@ spec:
|
||||
- name: BAO_FIELD
|
||||
value: token
|
||||
- name: WOODPECKER_URL
|
||||
value: http://woodpecker.apps.svc.cluster.local:8000
|
||||
value: http://woodpecker.woodpecker.svc.cluster.local:8000
|
||||
- name: WOODPECKER_ORG
|
||||
value: k.renner
|
||||
- name: WOODPECKER_SECRET_NAME
|
||||
|
||||
Reference in New Issue
Block a user