Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate key "command" for crowdsec-agent container in helm chart 0.16.0 #224

Open
Eyeless77 opened this issue Jan 9, 2025 · 3 comments
Assignees
Labels
kind/bug Something isn't working triage/accepted Triaged

Comments

@Eyeless77
Copy link

I use Flux CD to manage my crowdsec helm release. When I use chart version 0.16.0 I get an error:

crowdsec with chart [email protected]: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors: line 118: mapping key "command" already defined at line 64

My values are the following:

...
agent:
  acquisition:
    - namespace: "traefik"
      podName: "traefik-*"
      program: "traefik"
      poll_without_inotify: true
  resources:
    limits:
      memory: 500Mi
    requests:
      cpu: 150m
      memory: 100Mi
  persistence:
    config:
      enabled: true
      accessModes:
        - ReadWriteMany
      storageClassName: "freenas-nfs-csi"
      size: 100Mi
  env:
    - name: PARSERS
      value: "crowdsecurity/cri-logs crowdsecurity/traefik-logs"
    - name: COLLECTIONS
      value: "crowdsecurity/traefik"
...

I tried to comment out different parts of my values and figured out that removing persistense section fixes that issue. With the same values I can successfully install crowdsec with chart version 0.15.0.

I checked diff between charts and I guess here is the problem.

When .Values.tls.enabled is false and .Values.agent.persistentVolume.config.enabled is true (as I use in my setup), we've got duplicate command for agent container.

Copy link

github-actions bot commented Jan 9, 2025

@Eyeless77: Thanks for opening an issue, it is currently awaiting triage.

If you haven't already, please provide the following information:

  • kind : bug, enhancementor documentation
  • area : agent, appsec, configuration, cscli, local-api

In the meantime, you can:

  1. Check Crowdsec Documentation to see if your issue can be self resolved.
  2. You can also join our Discord.
  3. Check Releases to make sure your agent is on the latest version.
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.

Copy link

github-actions bot commented Jan 9, 2025

@Eyeless77: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

  • /kind bug
  • /kind documentation
  • /kind enhancement
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the forked project rr404/oss-governance-bot repository.

@github-actions github-actions bot added the needs/kind Kind label required label Jan 9, 2025
@Eyeless77
Copy link
Author

/kind bug

@github-actions github-actions bot added kind/bug Something isn't working and removed needs/kind Kind label required labels Jan 9, 2025
@LaurenceJJones LaurenceJJones added triage/accepted Triaged and removed needs/triage Needs triage labels Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working triage/accepted Triaged
Projects
None yet
Development

No branches or pull requests

2 participants