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

ArgoCD notifications unable to be configured #1756

Open
SamuelLHuber opened this issue Oct 12, 2024 · 1 comment
Open

ArgoCD notifications unable to be configured #1756

SamuelLHuber opened this issue Oct 12, 2024 · 1 comment
Labels
community Issue made by a community member question Further information is requested

Comments

@SamuelLHuber
Copy link

Describe the bug: One is unable to configure the argocd notifications controller to recieve notifications to get notified about argocd doing work

To Reproduce
Steps to reproduce the behavior:

  1. Go to '
    notifications:
    '
  2. See that the chart supports notifications
  3. in the otomi values repo adjust the values/env/apps/argocd.yaml file with notification values
  4. See that the the argo notifications controller doesn't update.
  5. open argocd app and check the argocd values shown in the ui and see that your changes are never applied and used

Expected behavior: either via values for the apl helm chart or when adjusting the values in the otomi-values repository one should be allowed to configure notifications for argocd

Screenshots: (if applicable, add screenshots to help explain your problem)

Cluster(s):

  • Cloud: custom

Versions: (seen in console's /settings)

  • Core Version [v3.0.0]
  • Kubernetes [v1.30.4+k3s1]
  • Console Version: [v3.0.0-rc.0]
  • API version: [3.0.0-rc.0]
@SamuelLHuber SamuelLHuber added the bug Something isn't working label Oct 12, 2024
@j-zimnowoda
Copy link
Contributor

Hi @SamuelLHuber ,
Thanks for making us aware about your use case.

In the values/env/apps/argocd.yaml the top level parameters is an abstraction layer that the platform provides.
Users can still have full control over the helm chart values by defining the values under the _rawValues section.
In this particular case in the values/env/apps/argocd.yaml

# <top level values>
_rawValues:
  # any helm chart values that is applicable 
  notifications:
    <notification specific params>

The _rawValues has priority over top level values

@j-zimnowoda j-zimnowoda added question Further information is requested community Issue made by a community member and removed bug Something isn't working labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issue made by a community member question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants