Cannot install the plugin with ArgoCD

[mmelcot]

I try to install this plugin with ArgoCD like this:

---
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: cloudnativepg-operator
  namespace: argocd
  annotations:
    argocd.argoproj.io/sync-wave: '0'
  labels:
    type: postgres
spec:
  project: myproject
  sources:
    - chart: cloudnative-pg
      repoURL: https://cloudnative-pg.github.io/charts
      targetRevision: 0.28.2
      helm:
        releaseName: cloudnative-pg
    # Install the barman plugin
    - repoURL: https://github.com/cloudnative-pg/plugin-barman-cloud
      targetRevision: v0.13.0
      path: .
  destination:
    server: https://kubernetes.default.svc
    namespace: cnpg-system
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions: [CreateNamespace=true, ServerSideApply=true]

ArgoCD complains with:

ComparisonError: Failed to load target state: failed to unmarshal manifests for source 2 of 2: Object 'Kind' is missing in '{".":"0.13.0","metadata":{"annotations":{"argocd.argoproj.io/tracking-id":"cloudnativepg-operator:/:cnpg-system/"}}}'

[dosubot]

Hi @mmelcot! I'm Dosu and I'm helping the CloudNativePG team.

The issue is that pointing ArgoCD at the repository root (path: .) doesn't work because there's no Helm chart or top-level kustomization.yaml at the root — ArgoCD doesn't know how to interpret it as a valid source.

There are a couple of approaches that should work:

Option 1: Use the Kustomize directory

Point ArgoCD to the kubernetes/ directory (which contains a valid Kustomization) [1]:

- repoURL: https://github.com/cloudnative-pg/plugin-barman-cloud
  targetRevision: v0.13.0
  path: kubernetes

Option 2: Apply the pre-built manifest directly

Use the release manifest URL with a "raw YAML" approach. You can reference it as a multi-source with a directory type or apply it separately:

kubectl apply -f https://github.com/cloudnative-pg/plugin-barman-cloud/releases/download/v0.13.0/manifest.yaml

For ArgoCD specifically, Option 1 (pointing to kubernetes/ or config/default/) with Kustomize is likely the cleanest approach [2].

Note: there's no Helm chart available for this plugin yet — that's tracked as a feature request in issue #351 [3]. Also, make sure cert-manager is installed, as it's a requirement for the plugin [4].

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.