Replies: 1 comment
-
|
Support for Flux v1 ended years ago. If you want support from us you need to be planning to use Flux v2 (and not Argo 😅) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Team,
we are using flux v1 and we cant upgrade it to v2 as we are moving from flux to argo CD. Right now we are not getting notifications from flux to our teams channels using connectors. Is it possible we can send flux (commits and clusters name events) to datadog ?
I tried adaptive card but body template i used gave me 5xx errors in flux. fyi @shamjyothi
Patch for flux-slackbot.yaml where i tried new body template which is giving 500 errors in fluxcloud pod.
So currently, We are exploring options to send notifications to teams from flux v1 running in our EKS clusters. We are good to use Datadog if its possible for our use case. Since msteams connectors are depricated we are not getting notifications in teams channels with details like "cluster name, commit SHA, errors" etc. Please if you can suggest any approach that will work with v1, we can try that.
I can provide more details if required
Appreciate your support!
Beta Was this translation helpful? Give feedback.
All reactions