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

Helm validation schema is broken #211

Open
vst-name opened this issue Dec 6, 2024 · 6 comments
Open

Helm validation schema is broken #211

vst-name opened this issue Dec 6, 2024 · 6 comments
Assignees
Labels
needs/kind Kind label required needs/triage Needs triage

Comments

@vst-name
Copy link

vst-name commented Dec 6, 2024

Hi, i've run into the following issue.

$ helm upgrade --install --create-namespace -n crowdsec crowdsec crowdsec/crowdsec -f values.yaml 
Error: UPGRADE FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
crowdsec:
- agent.additionalAcquisition.0: Must validate at least one schema (anyOf)
- agent.additionalAcquisition.0: Additional property listen_addr is not allowed
- agent.additionalAcquisition.0: Additional property webhook_path is not allowed
- agent.additionalAcquisition.0.source: agent.additionalAcquisition.0.source does not match: "kinesis"

my values.yaml:

agent:
   ports:
   - name: k8s-audit
     containerPort: 9876
     protocol: TCP
   additionalAcquisition:
   - source: k8s-audit
     listen_addr: "0.0.0.0:9876"
     webhook_path: /k8s-audit
     labels:
       type: k8s-audit

Your example

Copy link

github-actions bot commented Dec 6, 2024

@vst-name: 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.

@github-actions github-actions bot added the needs/triage Needs triage label Dec 6, 2024
Copy link

github-actions bot commented Dec 6, 2024

@vst-name: 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 Dec 6, 2024
@srkoster
Copy link
Contributor

Hi @vst-name k8s-audit isn't a valid source type. What are you trying to monitor?

@LaurenceJJones
Copy link
Contributor

Hi @vst-name k8s-audit isn't a valid source type. What are you trying to monitor?

k8s-audit is valid from CrowdSec point of view https://docs.crowdsec.net/docs/next/log_processor/data_sources/kubernetes_audit ,however, the schema was written before this was a thing so most likely we need to update it.

@srkoster
Copy link
Contributor

@LaurenceJJones my bad, missed that part in the documentation. Thanks for pointing it out.

I've drafted a PR to modify the schema.

@vst-name
Copy link
Author

vst-name commented Dec 17, 2024

Thank you! I'll just close the issue on new chart version after confirming that the updated schema works, or you can close it yourself, by all means...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs/kind Kind label required needs/triage Needs triage
Projects
None yet
Development

No branches or pull requests

4 participants