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

At least one sink must be defined - Using ArgoCD #1357

Open
AlissonRS opened this issue Mar 25, 2024 · 2 comments
Open

At least one sink must be defined - Using ArgoCD #1357

AlissonRS opened this issue Mar 25, 2024 · 2 comments

Comments

@AlissonRS
Copy link

I used robusta CLI to generate a generated_values.yaml for me.

This is how it looks:

globalConfig:
  signing_key: <some_guid>
  account_id: <some_guid>
sinksConfig:
  - discord_sink:
      name: personal_discord_sink
      url: https://discord.com/api/webhooks/123456789
disableCloudRouting: true
runner:
  sendAdditionalTelemetry: true
clusterName: my-cluster

So it does have a sink (using my actual webhook URL), but installing it with Helm via ArgoCD produces the error below:

failed exit status 1: Error: execution error at (Robusta/charts/robusta/templates/playbooks-config.yaml:9:7): At least one sink must be defined! Use --debug flag to render out invalid YAML

From Argo UI we can see the parameter is detected (so it's properly formatted):

image

If I install the exact same values.yaml via helm CLI from my local machine, it works fine, it's only failing via Argo.

Not sure if it makes a difference, but it's actually being installed as a subchart as I'm using Argo's ApplicationSet.

Copy link

Hi 👋, thanks for opening an issue! Please note, it may take some time for us to respond, but we'll get back to you as soon as we can!

  • 💬 Slack Community: Join Robusta team and other contributors on Slack here.
  • 📖 Docs: Find our documentation here.
  • 🎥 YouTube Channel: Watch our videos here.

@aantn
Copy link
Collaborator

aantn commented Mar 26, 2024

Weird, not sure what is going on. Is there a way to get more debug info out of Argo?

Or could you share more details including the Argo ApplicationSet and any other relevant config?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants