-
Notifications
You must be signed in to change notification settings - Fork 260
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
Unable to deploy robusta helm chart with ArgoCD #1314
Comments
The solution ended up being using a separate values file, using a yaml file located in the repository instead of trying to inline in an argocd application directly. example: apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: robusta
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
destination:
server: https://kubernetes.default.svc
namespace: robusta
project: default
sources:
- chart: robusta
repoURL: https://robusta-charts.storage.googleapis.com
targetRevision: 0.10.31
helm:
valueFiles:
- $values/values/robusta.yaml |
Thanks, I'll update our docs accordingly. Can you explain what |
Thanks for getting the docs updated! I chopped off a few lines by mistake, here's the context on what sources:
- chart: robusta
repoURL: https://robusta-charts.storage.googleapis.com
targetRevision: 0.10.31
helm:
valueFiles:
- $values/values/robusta.yaml
- repoURL: "[email protected]:mckernanin/homelab.git"
targetRevision: HEAD
ref: values |
Got it, thanks. I've opened a new PR correcting it. If you could take a look, it would be greatly appreciated! |
Describe the bug
Original slack conversation: https://robustacommunity.slack.com/archives/C02R0LVANKY/p1707937278191989
I am unable to deploy robusta when using a yaml templated application for ArgoCD. As suggested on slack, I have tried a number of different ways to refer to my secret values, none of them have worked. Example yaml application for Argo to deploy the helm chart:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should be able to deploy Robusta and reference environment secrets
The text was updated successfully, but these errors were encountered: