Jaideep Rao
The argocd-notifications controller uses the argocd-notifications-cm configmap to manage notifications. The configmap contains the notification triggers configurations as well as the available notification templates. We will have some triggers/templates configured...
**Describe the bug** The Argo CD CR status section is currently missing a field to reflect the status of the applicationset controller. To be consistent with the rest of the...
**Describe the bug** ApplicationSet resources (deployment, serviceaccont, roles, rolebindings) are not deleted from cluster when appset controller is disabled by deleting `.spec.applicationSet` **To Reproduce** Steps to reproduce the behavior: 1....
Note on DCO: If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the *Details* link next to...
Signed-off-by: Jaideep Rao fixes: #152
Notifications-engine is currently consuming `v1.1.0` of the `goutils` package https://nvd.nist.gov/vuln/detail/CVE-2021-4238 has identified a critical vulnerability in this package concerning insecure randomness in the function `CryptoRandomAlphaNumeric` which is consumed by notifications-engine...
**What type of PR is this?** > Uncomment only one ` /kind` line, and delete the rest. > For example, `> /kind bug` would simply become: `/kind bug` > /kind...
Hi all First off, thanks for being a part of the Argo CD Operator community. We appreciate everyone's contribution and involvement in making this project what it is today! As...
I think it would be beneficial to consider a segmented package structure for the existing controllers package, in a way that would make the code more organized and abstracted by...
# What does this PR do? Converts blocking calls to async calls within the following providers/components: - runpod (inference) - sentence_transformers (inference) - litellm (inference) [//]: # (If resolving an...