fix(forgejo): force-replace argocd-deploy-key-init Job
Replace=true alone uses kubectl replace, which rejects updates on Job immutable fields (spec.selector, spec.template.metadata.labels) when the cluster already has a Job with auto-generated values. Add Force=true so ArgoCD does kubectl replace --force (delete + recreate). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
85b8fec6b3
commit
bf0cf0a11d
|
|
@ -41,7 +41,7 @@ metadata:
|
|||
namespace: #@ ns
|
||||
annotations:
|
||||
argocd.argoproj.io/sync-wave: "1"
|
||||
argocd.argoproj.io/sync-options: Replace=true
|
||||
argocd.argoproj.io/sync-options: Replace=true,Force=true
|
||||
spec:
|
||||
ttlSecondsAfterFinished: 300
|
||||
template:
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ kind: Job
|
|||
metadata:
|
||||
annotations:
|
||||
a8r.io/repository: ssh://git@git.tr1ceracop.de:222/gitea_admin/k8s-and-chill.git
|
||||
argocd.argoproj.io/sync-options: Replace=true
|
||||
argocd.argoproj.io/sync-options: Replace=true,Force=true
|
||||
argocd.argoproj.io/sync-wave: "1"
|
||||
name: argocd-deploy-key-init
|
||||
namespace: forgejo
|
||||
|
|
|
|||
Loading…
Reference in a new issue