linode / linode/apl-core

ArgoCD notifications unable to be configured

Open
#1,756 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community question
Dominant language
Go Template
Stars
2.3k
Forks
186
Avg merge
3d 11h
Merged PRs (30d)
66

Description

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 'https://github.com/linode/apl-core/blob/3c393d4c579cf99b7d40b2aa18280f644877641d/charts/argocd/values.yaml#L2934'
  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]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the ArgoCD chart values near line 2934 in the referenced apl-core values.yaml and compare them with values/env/apps/argocd.yaml in the otomi-values repository. Inspect how the notification values are rendered in the ArgoCD application and verify that the notifications controller receives and applies them. Done means notification configuration can be supplied through either supported values path and is reflected in the running controller.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.