Skip to content

Commit 8864268

Browse files
authored
Merge branch 'main' into clean-up-metadata
2 parents fa9a1d8 + a1fc2a8 commit 8864268

File tree

6 files changed

+361
-281
lines changed

6 files changed

+361
-281
lines changed

content/agent/configuration/configure-nginx-agent-group.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ type:
1212

1313
During installation, NGINX Agent detects the NGINX user (typically `nginx`) for the master and worker processes and adds this user to a group called `nginx-agent`.
1414

15-
If you change the NGINX username after installing the NGINX Agent, you'll need to add the new username to the `nginx-agent` group so that the NGINX socket has the proper permissions.
15+
If you change the NGINX username after installing NGINX Agent, you'll need to add the new username to the `nginx-agent` group so that the NGINX socket has the proper permissions.
1616

1717
A failure to update the `nginx-agent` group when the NGINX username changes may result in non-compliance errors for NGINX Plus.
1818

content/ngf/how-to/traffic-security/integrating-cert-manager.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,10 @@ The first step is to deploy cert-manager onto the cluster.
6868
cert-manager jetstack/cert-manager \
6969
--namespace cert-manager \
7070
--create-namespace \
71-
--version v1.12.0 \
72-
--set installCRDs=true \
73-
--set "extraArgs={--feature-gates=ExperimentalGatewayAPISupport=true}"
71+
--set config.apiVersion="controller.config.cert-manager.io/v1alpha1" \
72+
--set config.kind="ControllerConfiguration" \
73+
--set config.enableGatewayAPI=true \
74+
--set crds.enabled=true
7475
```
7576

7677
---

content/nginx-one/changelog.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,19 @@ Stay up-to-date with what's new and improved in the F5 NGINX One Console.
3232

3333
## January 20, 2025
3434

35+
### Manage certificates with Config Sync Groups
36+
37+
With the NGINX One Console, you can now manage certificate deployment in Config Sync Groups.
38+
39+
You can:
40+
41+
- Add a certificate to a Config Sync Group
42+
- Remove a deployed certificate from a Config Sync Group
43+
44+
For more information, including warnings about risks, see our documentation on how you can:
45+
- [Add a file]({{< ref "/nginx-one/how-to/nginx-configs/add-file.md" >}})
46+
- [Manage certificates]({{< ref "/nginx-one/how-to/certificates/manage-certificates.md" >}})
47+
3548
### Revert a configuration
3649

3750
Using the NGINX One Console you can now:

content/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ If you need to deactivate a data plane key before its expiration date, follow th
6060

6161
## Delete a data plane key
6262

63-
Before you can delete a key, it must be expired or revoked. You can revoke a key either through the NGINX One console, as explained above, or by using the REST API. Once deleted, all information about the data plane key is permanently removed.
63+
Before you can delete a key, it must be expired or revoked. You can revoke a key either through the NGINX One Console, as explained above, or by using the REST API. Once deleted, all information about the data plane key is permanently removed.
6464

6565
1. On the left menu, select **Data Plane Keys**.
6666
2. Find the key you want to revoke in the list of expired or revoked keys.

0 commit comments

Comments
 (0)