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

notifications #317

Closed
asloan7 opened this issue Mar 26, 2021 · 13 comments
Closed

notifications #317

asloan7 opened this issue Mar 26, 2021 · 13 comments

Comments

@asloan7
Copy link
Contributor

asloan7 commented Mar 26, 2021

Does fleet have a way to send notifications (to slack, email, etc.) upon the updating or failure of a deployed resource?

@strowi
Copy link

strowi commented Dec 30, 2021

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 kubectl wait.

@telderfts
Copy link

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?

@sub2u
Copy link

sub2u commented Jun 20, 2022

Does anyone have an alternative approach to achieving this with fleet integration?
Monitoring release success or failure is challenging without proper alert or notification.

@kkaempf kkaempf closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2022
@zube zube bot closed this as completed Dec 13, 2022
@telderfts
Copy link

telderfts commented Dec 13, 2022

@kkaempf Can you explain why this was closed as not planned since this is a highly requested feature and needed?

@kkaempf
Copy link
Collaborator

kkaempf commented Dec 14, 2022

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 😉

@asloan7
Copy link
Contributor Author

asloan7 commented Dec 14, 2022

I'm still interested

@asloan7
Copy link
Contributor Author

asloan7 commented Dec 14, 2022

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
https://fluxcd.io/flux/guides/notifications/
https://argocd-notifications.readthedocs.io/en/stable/

@zube zube bot removed the [zube]: Done label Mar 14, 2023
@billhong-just
Copy link

I'm still interested too. 👀

@BoyFromDubai
Copy link

I'm interested as well

1 similar comment
@gouravsw
Copy link

I'm interested as well

@telderfts
Copy link

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 https://fluxcd.io/flux/guides/notifications/ https://argocd-notifications.readthedocs.io/en/stable/

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.

@youvegotmoxie
Copy link

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.

@strowi
Copy link

strowi commented Apr 12, 2024

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants