From 100e20502b860ba04147a39b73474ba333b8e739 Mon Sep 17 00:00:00 2001 From: Venktesh Date: Wed, 17 Apr 2024 10:26:25 +0100 Subject: [PATCH 1/2] fix link to rbac template --- docs/content/configuration/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/configuration/security.md b/docs/content/configuration/security.md index 728eab2f68..2b827fb76e 100644 --- a/docs/content/configuration/security.md +++ b/docs/content/configuration/security.md @@ -24,7 +24,7 @@ The Ingress Controller requires a service account which is configured using RBAC We strongly recommend using the [RBAC configuration](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/deployments/rbac/rbac.yaml) provided in our standard deployment configuration. It is configured with the least amount of privilege required for the Ingress Controller to work. We strongly recommend inspecting the RBAC configuration for [Manifests](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/deployments/rbac/rbac.yaml) -or for [Helm](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/charts/nginx-ingress/templates/rbac.yaml) to understand what access the Ingress Controller service account has and to which resources. For example, by default the service account has access to all Secret resources in the cluster. +or for [Helm](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/charts/nginx-ingress/templates/controller-role.yaml) to understand what access the Ingress Controller service account has and to which resources. For example, by default the service account has access to all Secret resources in the cluster. ### Certificates and Privacy Keys From ab3945c212e30e803e737a01ed8f0ee1502c4e7a Mon Sep 17 00:00:00 2001 From: Venktesh Date: Wed, 17 Apr 2024 10:43:09 +0100 Subject: [PATCH 2/2] fix link to rbac template --- docs/content/configuration/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/configuration/security.md b/docs/content/configuration/security.md index 2b827fb76e..68779c0df5 100644 --- a/docs/content/configuration/security.md +++ b/docs/content/configuration/security.md @@ -24,7 +24,7 @@ The Ingress Controller requires a service account which is configured using RBAC We strongly recommend using the [RBAC configuration](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/deployments/rbac/rbac.yaml) provided in our standard deployment configuration. It is configured with the least amount of privilege required for the Ingress Controller to work. We strongly recommend inspecting the RBAC configuration for [Manifests](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/deployments/rbac/rbac.yaml) -or for [Helm](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/charts/nginx-ingress/templates/controller-role.yaml) to understand what access the Ingress Controller service account has and to which resources. For example, by default the service account has access to all Secret resources in the cluster. +or for [Helm](https://github.com/nginxinc/kubernetes-ingress/blob/v3.5.0/charts/nginx-ingress/templates/clusterrole.yaml) to understand what access the Ingress Controller service account has and to which resources. For example, by default the service account has access to all Secret resources in the cluster. ### Certificates and Privacy Keys