Repository navigation
cert-manager install retries exhausted #3
Copy link
Copy link
Closed
Description
Sometimes you can see the error:
Name: cert-manager
Namespace: cozy-cert-manager
Labels: <none>
Annotations: <none>
API Version: helm.toolkit.fluxcd.io/v2beta1
Kind: HelmRelease
Metadata:
Creation Timestamp: 2024-01-26T10:02:21Z
Finalizers:
finalizers.fluxcd.io
Generation: 1
Resource Version: 2778687
UID: 941ed833-db28-40bd-82f5-e01a895d3dd7
Spec:
Chart:
Spec:
Chart: cozy-cert-manager
Reconcile Strategy: ChartVersion
Source Ref:
Kind: HelmRepository
Name: cozystack-system
Namespace: cozy-system
Version: *
Depends On:
Name: cilium
Namespace: cozy-cilium
Name: kubeovn
Namespace: cozy-kubeovn
Interval: 1m
Release Name: cert-manager
Status:
Conditions:
Last Transition Time: 2024-01-26T13:33:07Z
Message: install retries exhausted
Reason: InstallFailed
Status: False
Type: Ready
Last Transition Time: 2024-01-26T13:33:07Z
Message: Helm install failed: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "certificaterequests.cert-manager.io" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "cert-manager"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "cozy-cert-manager"
Last Helm logs:
Reason: InstallFailed
Status: False
Type: Released
Failures: 310
Helm Chart: cozy-system/cozy-cert-manager-cert-manager
Install Failures: 1
Last Attempted Revision: 1.0.0
Last Attempted Values Checksum: da39a3ee5e6b4b0d3255bfef95601890afd80709
Observed Generation: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning error 10m (x71 over 15h) helm-controller reconciliation failed: install retries exhausted
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
gecube commentedon Jan 29, 2024
installCRDsflag tofalseand install CRDs separately in a different Kustomization overlay.In this way we can fix this transient issue.
kvaps commentedon Jan 29, 2024
Separating CRDs from the main Helm chart definitely makes sense
kvaps commentedon Feb 20, 2024
currently fixed by:
fix(operator): force source-watcher drift via status patch, not reque…
feat(kamaji): default to 2 replicas, drop telemetry webhook (#2671)
fix(operator): force source-watcher drift via status patch, not reque…
fix(operator): hold final backoff window before give-up, note upstrea…
fix(operator): force source-watcher drift via status patch, not reque…
fix(operator): hold final backoff window before give-up, note upstrea…
fix(operator): force source-watcher drift via status patch, not reque…
fix(operator): hold final backoff window before give-up, note upstrea…
fix(kubernetes): re-pin deleted centos:stream9 digest for kubevirt-cs…