Skip to content

Commit 0825f18

Browse files
committed
Update document to shift the subject focus the Policy object
1 parent aed5fbd commit 0825f18

File tree

2 files changed

+9
-11
lines changed

2 files changed

+9
-11
lines changed
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
# Deploy an Access Control policy
1+
# Deploy a Policy for access control
22

3-
This is the example code used in the [Deploy an Access Control policy](https://docs.nginx.com/nginx-ingress-controller/configuration/access-control/) documentation.
3+
This is the example code used in the [Deploy a Policy for access control](https://docs.nginx.com/nginx-ingress-controller/configuration/access-control/) documentation.

site/content/configuration/access-control.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,11 @@
11
---
2-
title: Deploy an Access Control policy
2+
title: Deploy a Policy for access control
33
weight: 900
44
toc: true
55
docs: DOCS-000
66
---
77

8-
This topic describes how to apply and update an Access Control policy with F5 NGINX Ingress Controller.
9-
10-
It demonstrates this using an example application and a [VirtualServer custom resource]({{< ref "/configuration/virtualserver-and-virtualserverroute-resources.md" >}})
8+
This topic describes how to use F5 NGINX Ingress Controller to apply and update a Policy for access control. It demonstrates it using an example application and a [VirtualServer custom resource]({{< ref "/configuration/virtualserver-and-virtualserverroute-resources.md" >}}).
119

1210
---
1311

@@ -45,7 +43,7 @@ kubectl apply -f webapp.yaml
4543

4644
---
4745

48-
## Deploy an Access Control policy
46+
## Deploy a Policy to create a deny rule
4947

5048
Create a file named _access-control-policy-deny.yaml_. The highlighted _deny_ field will be used by the example application, and should be changed to the subnet of your machine.
5149

@@ -93,21 +91,21 @@ The *403* response is expected, successfully blocking your machine.
9391

9492
---
9593

96-
## Update the policy
94+
## Update the Policy to create an allow rule
9795

98-
Create a new policy with the file _access-control-policy-allow.yaml_, updating the _allow_ field to the subnet of your machine.
96+
Update the Policy with the file _access-control-policy-allow.yaml_, setting the _allow_ field to the subnet of your machine.
9997

10098
{{< ghcode "https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/refs/heads/main/examples/custom-resources/access-control/access-control-policy-allow.yaml" "hl_lines=7-8" >}}
10199

102-
Apply the policy:
100+
Apply the Policy:
103101

104102
```shell
105103
kubectl apply -f access-control-policy-allow.yaml
106104
```
107105

108106
----
109107

110-
## Verify the policy update
108+
## Verify the Policy update
111109

112110
Attempt to access the application again:
113111

0 commit comments

Comments
 (0)