From dd1b9d00e331eaab5ce90dee65a92ec46fe7c152 Mon Sep 17 00:00:00 2001
From: Michel Tomas <michel@kissmy.co>
Date: Fri, 23 Apr 2021 01:19:22 +0200
Subject: [PATCH] docs: fix outdated anti-affinity docs

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 8d966676..71608dd7 100644
--- a/README.md
+++ b/README.md
@@ -637,11 +637,11 @@ In order to configure a static etcd cluster to scrape there is a simple [kube-pr
 ### Pod Anti-Affinity
 
 To prevent `Prometheus` and `Alertmanager` instances from being deployed onto the same node when
-possible, one can include the [kube-prometheus-anti-affinity.libsonnet](jsonnet/kube-prometheus/kube-prometheus-anti-affinity.libsonnet) mixin:
+possible, one can include the [kube-prometheus-anti-affinity.libsonnet](jsonnet/kube-prometheus/addons/anti-affinity.libsonnet) mixin:
 
 ```jsonnet
 (import 'kube-prometheus/kube-prometheus.libsonnet') +
-(import 'kube-prometheus/kube-prometheus-anti-affinity.libsonnet')
+(import 'kube-prometheus/addons/anti-affinity.libsonnet')
 ```
 
 ### Stripping container resource limits
-- 
GitLab