From fc59ddb628866199ba77c6fd3ec6f5d6264ab8a2 Mon Sep 17 00:00:00 2001
From: Sergio Ballesteros <snaker@locolandia.net>
Date: Tue, 6 Sep 2022 17:48:57 +0200
Subject: [PATCH] Fix README links

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9a3fbad6c..0fe4d9812 100644
--- a/README.md
+++ b/README.md
@@ -152,7 +152,7 @@ This behavior is configurable, creating a configmap and indicating to use it. An
 
 By default Kubernetes will run containers as the user specified in the Dockerfile (or the root user if not specified), this is not always desirable.
 If you need the containers to run as a specific user (or provide any other PodSecurityContext options) then you can specify a custom `securityContext` in the
-`redisfailover` object. See the [SecurityContext example file](example/redisfailover/security-context.yaml) for an example. Keys available under securityContext are detailed [here](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.14/#podsecuritycontext-v1-core)
+`redisfailover` object. See the [SecurityContext example file](example/redisfailover/security-context.yaml) for an example. You can visit kubernetes documentation for detailed docs about [security context](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/)
 
 ### Custom containerSecurityContext at container level
 
-- 
GitLab