Merge branch 'mainframe-mod-ref-testing' into update-icon-usage

Author: lamATnginx

_banners/eos-acm.md

@@ -0,0 +1,8 @@
+{{< banner "warning" "End of Sale Notice:" >}}
+  <br>
+  F5 NGINX is announcing the <strong>End of Sale (EoS)</strong> for NGINX Management Suite API Connectivity Manager Module, <strong>effective January 1, 2024</strong>.
+  <br><br>
+  F5 maintains generous lifecycle policies that allow customers to continue support and receive product updates. Existing API Connectivity Manager Module customers can continue to use the product past the EoS date. <strong>License renewals are not available after September 30, 2024.</strong>
+  <br><br>
+  See our <a href="https://my.f5.com/manage/s/article/K000137989">End of Sale announcement</a> for more details.
+{{</ banner >}}

_banners/eos-mesh.md

@@ -1,8 +1,8 @@
 {{< banner "warning" "End of Sale Notice:" >}}
-  <br>
-  F5 NGINX is announcing the <strong>End of Sale (EoS)</strong> for NGINX Management Suite API Connectivity Manager Module, <strong>effective January 1, 2024</strong>.
-  <br><br>
-  F5 maintains generous lifecycle policies that allow customers to continue support and receive product updates. Existing API Connectivity Manager Module customers can continue to use the product past the EoS date. <strong>License renewals are not available after September 30, 2024.</strong>
-  <br><br>
-  See our <a href="https://my.f5.com/manage/s/article/K000137989">End of Sale announcement</a> for more details.
+  <p>
+    Commercial support for NGINX Service Mesh is available to customers who currently have active NGINX Microservices Bundle subscriptions. F5 NGINX announced the End of Sale (EoS) for the NGINX Microservices Bundles as of <strong>July 1, 2023</strong>.
+  </p>
+  <p>
+    See our <a href="https://my.f5.com/manage/s/article/K000135468">End of Sale announcement</a> for more details.
+  </p>
 {{</ banner >}}

content/agent/_index.md

@@ -9,4 +9,50 @@ cascade:
     start-date: 2025-05-29
     end-date: 2025-09-09
     md: /_banners/agent-v3-release.md
+# The subtitle displays directly underneath the heading of a given page
+nd-subtitle:
+# Indicates that this is a custom landing page
+nd-landing-page: true
+# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
+nd-content-type: landing-page
+# Intended for internal catalogue and search, case sensitive:
+# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
+nd-product: Agent
 ---
+
+## About
+
+NGINX Agent is a companion daemon for your NGINX Open Source or NGINX Plus instance. It enables remote management of NGINX
+configurations, collection and reporting of real-time NGINX performance and operating system metrics, and notifications of NGINX events.
+
+[//]: # "This initial section introduces the product to a reader: give a short 1-2 sentence summary of what the product does and its value to the reader."
+[//]: # "Name specific functionality it provides: avoid ambiguous descriptions such as 'enables efficiency', focus on what makes it unique."
+
+## Featured content
+[//]: # "You can add a maximum of three cards: any extra will not display."
+[//]: # "One card will take full width page: two will take half width each. Three will stack like an inverse pyramid."
+[//]: # "Some examples of content could be the latest release note, the most common install path, and a popular new feature."
+
+{{<card-layout>}}
+  {{<card-section showAsCards="true" isFeaturedSection="true">}}
+    {{<card title="About" titleUrl="/nginx-agent/about" icon="info">}}
+      Learn everything you need to know about NGINX Agent
+    {{</card>}}
+    <!-- The titleURL and icon are both optional -->
+    <!-- Lucide icon names can be found at https://lucide.dev/icons/ -->
+    {{<card title="Getting started" titleUrl="/nginx-agent/installation-upgrade/getting-started" icon="unplug">}}
+      Install NGINX Agent and run a mock control plane
+    {{</card>}}
+  {{</card-section>}}
+{{</card-layout>}}
+
+{{<card-layout>}}
+  {{<card-section showAsCards="true" isFeaturedSection="true">}}
+    {{<card title="Upgrade" titleUrl="/nginx-agent/installation-upgrade/upgrade/" icon="circle-fading-arrow-up">}}
+    {{</card>}}
+    {{<card title="Configuration" titleUrl="/nginx-agent/configuration" icon="cog">}}
+    {{</card>}}
+    {{<card title="Support" titleUrl="/nginx-agent/support" icon="hand-helping">}}
+    {{</card>}}
+  {{</card-section>}}
+{{</card-layout>}}

content/ngf/get-started.md

@@ -132,13 +132,76 @@ The YAML code in the following sections can be found in the [cafe-example folder
 
 ### Create the application resources
 
-Create the file _cafe.yaml_ with the following contents:
-
-{{< ghcode `https://raw.githubusercontent.com/nginx/nginx-gateway-fabric/refs/heads/main/examples/cafe-example/cafe.yaml`>}}
-
-Apply it using `kubectl`:
-
-```shell
+Run the following command to create the file _cafe.yaml_, which is then used to deploy the *coffee* application to your cluster:
+
+```yaml
+cat <<EOF > cafe.yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: coffee
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: coffee
+  template:
+    metadata:
+      labels:
+        app: coffee
+    spec:
+      containers:
+      - name: coffee
+        image: nginxdemos/nginx-hello:plain-text
+        ports:
+        - containerPort: 8080
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: coffee
+spec:
+  ports:
+  - port: 80
+    targetPort: 8080
+    protocol: TCP
+    name: http
+  selector:
+    app: coffee
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: tea
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app: tea
+  template:
+    metadata:
+      labels:
+        app: tea
+    spec:
+      containers:
+      - name: tea
+        image: nginxdemos/nginx-hello:plain-text
+        ports:
+        - containerPort: 8080
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: tea
+spec:
+  ports:
+  - port: 80
+    targetPort: 8080
+    protocol: TCP
+    name: http
+  selector:
+    app: tea
+EOF
 kubectl apply -f cafe.yaml
 ```
 
@@ -163,13 +226,22 @@ tea-6fbfdcb95d-9lhbj      1/1     Running   0          9s
 
 ### Create Gateway and HTTPRoute resources
 
-Create the file _gateway.yaml_ with the following contents:
-
-{{< ghcode `https://raw.githubusercontent.com/nginx/nginx-gateway-fabric/refs/heads/main/examples/cafe-example/gateway.yaml`>}}
-
-Apply it using `kubectl`:
-
-```shell
+Run the following command to create the file _gateway.yaml_, which is then used to deploy a Gateway to your cluster:
+
+```yaml
+cat <<EOF > gateway.yaml
+apiVersion: gateway.networking.k8s.io/v1
+kind: Gateway
+metadata:
+  name: gateway
+spec:
+  gatewayClassName: nginx
+  listeners:
+  - name: http
+    port: 80
+    protocol: HTTP
+    hostname: "*.example.com"
+EOF
 kubectl apply -f gateway.yaml
 ```
 
@@ -190,13 +262,48 @@ gateway-nginx-66b5d78f8f-4fmtb   1/1     Running   0          13s
 tea-6fbfdcb95d-9lhbj             1/1     Running   0          31s
 ```
 
-Create the file _cafe-routes.yaml_ with the following contents:
-
-{{< ghcode `https://raw.githubusercontent.com/nginx/nginx-gateway-fabric/refs/heads/main/examples/cafe-example/cafe-routes.yaml`>}}
-
-Apply it using `kubectl`:
-
-```shell
+Run the following command to create the file _cafe-routes.yaml_. It is then used to deploy two *HTTPRoute* resources in your cluster: one each for _/coffee_ and _/tea_.
+
+```yaml
+cat <<EOF > cafe-routes.yaml
+apiVersion: gateway.networking.k8s.io/v1
+kind: HTTPRoute
+metadata:
+  name: coffee
+spec:
+  parentRefs:
+  - name: gateway
+    sectionName: http
+  hostnames:
+  - "cafe.example.com"
+  rules:
+  - matches:
+    - path:
+        type: PathPrefix
+        value: /coffee
+    backendRefs:
+    - name: coffee
+      port: 80
+---
+apiVersion: gateway.networking.k8s.io/v1
+kind: HTTPRoute
+metadata:
+  name: tea
+spec:
+  parentRefs:
+  - name: gateway
+    sectionName: http
+  hostnames:
+  - "cafe.example.com"
+  rules:
+  - matches:
+    - path:
+        type: Exact
+        value: /tea
+    backendRefs:
+    - name: tea
+      port: 80
+EOF
 kubectl apply -f cafe-routes.yaml
 ```
 

content/nginx/module-reference/_index.md

@@ -0,0 +1,4 @@
+---
+title: NGINX Module Reference
+description:
+---

content/nginx/module-reference/http/_index.md

@@ -0,0 +1,4 @@
+---
+title: NGINX HTTP Reference
+description:
+---

content/nginx/module-reference/http/ngx_http_access_module.md

@@ -0,0 +1,89 @@
+---
+title: ngx_http_access_module
+description: ngx_http_access_module
+toc: true
+nd-org-source: http/ngx_http_access_module.xml
+nd-plus: false
+nd-partial-plus: false
+---
+
+
+<!--
+      ********************************************************************************
+      🛑 WARNING: AUTOGENERATED FILE - DO NOT EDIT 🛑 This Markdown file was
+      automatically generated from the source XML documentation. Any manual
+      changes made directly to this file will be overwritten. To request or
+      suggest changes, please edit the source XML files instead.
+      https://github.com/nginx/nginx.org/tree/main/xml/en
+      ********************************************************************************
+      -->
+
+
+The `ngx_http_access_module` module allows
+limiting access to certain client addresses.
+
+Access can also be limited by
+[password](/nginx/module-reference/http/ngx_http_auth_basic_module), by the
+[result of subrequest](/nginx/module-reference/http/ngx_http_auth_request_module),
+or by [JWT](/nginx/module-reference/http/ngx_http_auth_jwt_module).
+Simultaneous limitation of access by address and by password is controlled
+by the [satisfy](/nginx/module-reference/http/ngx_http_core_module#satisfy) directive.
+## Example Configuration
+
+
+```nginx
+location / {
+    deny  192.168.1.1;
+    allow 192.168.1.0/24;
+    allow 10.1.1.0/16;
+    allow 2001:0db8::/32;
+    deny  all;
+}
+
+```
+
+
+The rules are checked in sequence until the first match is found.
+In this example, access is allowed only for IPv4 networks
+`10.1.1.0/16` and `192.168.1.0/24`
+excluding the address `192.168.1.1`,
+and for IPv6 network `2001:0db8::/32`.
+In case of a lot of rules, the use of the
+[ngx_http_geo_module](/nginx/module-reference/http/ngx_http_geo_module)
+module variables is preferable.
+## Directives
+
+### allow
+
+{{< call-out >}}
+
+**Syntax:** allow `address` | `CIDR` | `unix:` | `all`
+
+**Default:** -
+
+**Context:** http, server, location, limit_except
+
+
+{{</call-out>}}
+
+
+Allows access for the specified network or address.
+If the special value `unix:` is specified (1.5.1),
+allows access for all UNIX-domain sockets.
+### deny
+
+{{< call-out >}}
+
+**Syntax:** deny `address` | `CIDR` | `unix:` | `all`
+
+**Default:** -
+
+**Context:** http, server, location, limit_except
+
+
+{{</call-out>}}
+
+
+Denies access for the specified network or address.
+If the special value `unix:` is specified (1.5.1),
+denies access for all UNIX-domain sockets.