https://rancher.com/ logo
Title
a

aloof-honey-35027

09/28/2022, 2:30 PM
Hi, We are using Rancher + Fleet (GitOps) + k3s in a relatively large setup (multi-cluster + 100s of nodes). Something that we struggle with is feedback, e.g lack of information flow back to Github (where our GitOps repo is based). Today I was reading the documentation (­čś▓), and stumbled over this:
The
fleet-agent
will continue to monitor the application bundle and report statuses back in the following order: bundledeployment > bundle > GitRepo > cluster.
(https://fleet.rancher.io/examples/) Is the fleet-agent able to report back to GitRepo? Is there any additional information on this? Appricate your support and feedback.
m

many-area-51777

09/28/2022, 3:33 PM
Which information would you want it to report back?
a

aloof-honey-35027

09/29/2022, 6:07 AM
What I am looking for is a way to report back Bundle state transations back to e.g the pull-request in the git repo which which is the source of the GitOps process. i.e the following state transition: Ready -> WaitModified -> NotReady -> Ready/ErrApply
I know this information is available in Rancher, but would like a user experience where only one location is required for GitOps changes, but also to monitoring progress of your updates.
m

many-area-51777

10/01/2022, 5:18 PM
You can maybe create a CronJob or even better, a custom operator, that connects to rancher's API, take this information and report it to a messaging system. @aloof-honey-35027