πŸ’­ poolers.postgresql.cnpg.io CRD metadata.annotations Too long Β·... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ !https://github.com/cloudnative-pg/charts/issues/325 Date: January 21, 2025 Image: poolers.postgresql.cnpg.io CRD metadata.annotations Too long Β· Issue #325 Β· cloudnative-pg/charts β€” Unable to deploy helm chart using ArgoCD. Getting following error Failed sync attempt to : one or more objects failed to apply, reason: CustomResourceDefinition.apiextensions.k8s.io "poolers.postgr... poolers.postgresql.cnpg.io CRD metadata.annotations Too long Β· Issue #325 Β· cloudnative-pg/charts Unable to deploy helm chart using ArgoCD. Getting following error Failed sync attempt to : one or more objects failed to apply, reason: CustomResourceDefinition.apiextensions.k8s.io "poolers.postgr... GitHub Β· github.com I’ve never seen or needed to use a serversideapply in kubernetes before, but I ran into this same issue in my k3s homelab </homelab/> while installing cloudnative-pg. You can do it with argo [code] apiVersion: argoproj.io/v1alpha1 kind: Application spec: syncPolicy: syncOptions: - ServerSideApply=true and you can do it with kubectl [code] kubectl apply --server-side --force-conflicts -f cnpg-1.25.0.yaml NOTE β”‚ This post is a thought </thoughts/>. It’s a short note that I make about someone else’s content online #thoughts </tags/thoughts/>