From a2c709226860c53350fc923972db42f7356d8406 Mon Sep 17 00:00:00 2001 From: Matheus Pimenta Date: Fri, 14 Jun 2024 09:34:30 +0100 Subject: [PATCH] Update rfcs/0007-custom-event-metadata-from-annotations/README.md Co-authored-by: Sunny Signed-off-by: Matheus Pimenta --- rfcs/0007-custom-event-metadata-from-annotations/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/0007-custom-event-metadata-from-annotations/README.md b/rfcs/0007-custom-event-metadata-from-annotations/README.md index 3fe7908c32..a899078632 100644 --- a/rfcs/0007-custom-event-metadata-from-annotations/README.md +++ b/rfcs/0007-custom-event-metadata-from-annotations/README.md @@ -39,7 +39,7 @@ and have those fields sent to notification-controller as metadata on the event p In this proposal we **do not** aim to provide a method for Flux users to send etcd-indexed custom metadata fields from Flux objects in events to notification-controller, most specifically labels. By design an event already contains enough identification information to locate the associated Flux object inside the cluster, -which covers the use case of labels. Flux does not wish to incentive practices that are impactful to clusters +which covers the use case of labels. Flux does not wish to incentivize practices that are impactful to clusters without a strong reason or benefit. ## Proposal