Skip to content

Commit ed05fa0

Browse files
Bump fluxcd/notification-controller to latest release
1 parent e7cfbf9 commit ed05fa0

4 files changed

Lines changed: 6 additions & 6 deletions

File tree

UPSTREAM_PROJECTS.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,8 +117,8 @@ projects:
117117
go_version: "1.25"
118118
- name: notification-controller
119119
versions:
120-
- tag: v1.7.5
121-
go_version: "1.25"
120+
- tag: v1.8.1
121+
go_version: "1.26"
122122
- name: source-controller
123123
versions:
124124
- tag: v1.7.4
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
v1.7.5
1+
v1.8.1
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
1.25
1+
1.26

projects/fluxcd/notification-controller/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
## **Notification Controller**
2-
![Version](https://img.shields.io/badge/version-v1.7.5-blue)
2+
![Version](https://img.shields.io/badge/version-v1.8.1-blue)
33
![Build Status](https://codebuild.us-west-2.amazonaws.com/badges?uuid=eyJlbmNyeXB0ZWREYXRhIjoiVDhSNCt1djNtRytnWTgvQ01BMW13b2Y1YmZPakRrSGlRWitKZ0ZLZUdaS2xxclpLOFNidnBHNjBFWjRueHpOaGRrMzV5OUhLLzhRWHgyaC85R2tET2JZPSIsIml2UGFyYW1ldGVyU3BlYyI6IlZpNGwrazFrZndNMWE4cTciLCJtYXRlcmlhbFNldFNlcmlhbCI6MX0%3D&branch=main)
44

55
The [notification-controller](https://github.com/fluxcd/notification-controller) is a Kubernetes operator specialized in handling inbound and outbound events. The controller exposes an HTTP endpoint for receiving events from other controllers. It can be configured with Kubernetes custom resources such as `Alert`, `Event`,`Provider` and `Receiver` to define how events are processed and where to dispatch them.
@@ -15,7 +15,7 @@ about changes necessary to eks-anywhere to support the new version and/or automa
1515
eks-anywhere version reach out to @jiayiwang7 or @danbudris
1616
1. Update the `GIT_TAG` file to have the new desired version based on the upstream release tags.
1717
1. Compare the old tag to the new, looking specifically for Makefile changes.
18-
ex: [v1.2.2 compared to v1.7.5](https://github.com/fluxcd/notification-controller/compare/v1.2.2...v1.2.3). Check the `manager` target for
18+
ex: [v1.2.2 compared to v1.8.1](https://github.com/fluxcd/notification-controller/compare/v1.2.2...v1.2.3). Check the `manager` target for
1919
any build flag changes, tag changes, dependencies, etc.
2020
1. Verify the golang version has not changed. The version specified in `go.mod` seems to be kept up to date. There is also
2121
a [dockerfile](https://github.com/fluxcd/notification-controller/blob/main/Dockerfile#L5) they use for building which has it defined.

0 commit comments

Comments
 (0)