From 81c9fc43bff4807d201cb2eb977b69180f84dec8 Mon Sep 17 00:00:00 2001
From: kaitlynmichael <kaitlyn.michael@redis.com>
Date: Mon, 9 Sep 2024 07:50:23 -0500
Subject: [PATCH] fix relref

---
 content/operate/kubernetes/recommendations/node-selection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/operate/kubernetes/recommendations/node-selection.md b/content/operate/kubernetes/recommendations/node-selection.md
index e0ab641833..a001ce78df 100644
--- a/content/operate/kubernetes/recommendations/node-selection.md
+++ b/content/operate/kubernetes/recommendations/node-selection.md
@@ -28,7 +28,7 @@ Here are the ways that you can control the pod scheduling:
 
 ## Using node selectors
 
-The [`nodeSelector`]({{<relref "/operate/kubernetes/reference/redis_enterprise_cluster_api/#spec">}})
+The [`nodeSelector`]({{<relref "/operate/kubernetes/reference/redis_enterprise_cluster_api#spec">}})
 property of the cluster specification uses the same values and structures as
 the [Kubernetes `nodeSelector`](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector).
 In general, node labels are a simple way to make sure that specific nodes are used for Redis Enterprise pods.