cloudnative-pg / cloudnative-pg/plugin-barman-cloud

Cannot install the plugin with ArgoCD

Open
#980 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Go
Stars
192
Forks
75
Avg merge
1d 16h
Merged PRs (30d)
18

Description

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/"}}}'
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure using the shown ArgoCD Application and the repository at targetRevision v0.13.0. Inspect what ArgoCD finds in the repository root for source 2 and determine why it produces an object without a Kind. Done means ArgoCD can load valid manifests for the plugin source without the ComparisonError.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.