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
notifications #317
Comments
Was looking for the same feature, since those success/failures might currently go unnoticed unless using a external pipeline which would also need credentials for those clusters while doing sth. like |
Notifications of when a sync or deployment are ran should have been a day 1 feature. Does anyone have an idea or update as to when this might be available within fleet? |
Does anyone have an alternative approach to achieving this with fleet integration? |
@kkaempf Can you explain why this was closed as not planned since this is a highly requested feature and needed? |
With limited time and resources, we need to focus. Sorry. With just 4 people commenting, I don't think this is a highly requested feature. I'd be happy to review a pull request 😉 |
I'm still interested |
I understand everyone is super busy and overwhelmed, but fleet might have more uptake if it had some ProdOps-level visibility - or we just go looking at the alternatives like |
I'm still interested too. 👀 |
I'm interested as well |
1 similar comment
I'm interested as well |
We moved to ArgoCD...Fleet lacks a lot of what the more mature solutions have and not having some basic day 1 features isn't really promising. |
I switched to Flux in the 3 years this issue has been open. It doesn't seem like the Rancher team is taking Fleet very seriously since being able to be notified on a change is such a basic feature that every other CI/CD system has. |
@telderfts i tried looking at arogcd a while ago but couldn't find a good way to realize the pull-model (e.g. behind a firewall) instead of push with a central argocd instance. Did that change? |
Does fleet have a way to send notifications (to slack, email, etc.) upon the updating or failure of a deployed resource?
The text was updated successfully, but these errors were encountered: