Skip to content

Commit 97aea9f

Browse files
mjangsylwangADubhlaoich
authored
fix: N1C. Help users look for "out of sync" Instances in a CSG (#422)
* Point to Out of Sync Co-authored-by: Sylvia Wang <139922338+sylwang@users.noreply.github.com> Co-authored-by: Alan Dooley <a.dooley@f5.com> --------- Co-authored-by: Sylvia Wang <139922338+sylwang@users.noreply.github.com> Co-authored-by: Alan Dooley <a.dooley@f5.com>
1 parent 3e54134 commit 97aea9f

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

content/nginx-one/how-to/config-sync-groups/manage-config-sync-groups.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,12 @@ Now that you created a Config Sync Group, you can add instances to that group. A
100100

101101
Any instance that joins the group afterwards inherits that configuration.
102102

103+
{{< note >}} If you see the following [Config Sync Group Status](#config-sync-group-status) message: **Out of Sync**:
104+
105+
- Review the instance details in NGINX One Console to identify any publication problems.
106+
- After you change the configuration of the Config Sync Group, [Publish it](#publish-the-config-sync-group-configuration].
107+
In that case, review and resolve discrepancies between the Instance and the rest of the Config Sync Group. {{< /note >}}
108+
103109
### Add an existing instance to a Config Sync Group {#add-an-existing-instance-to-a-config-sync-group}
104110

105111
You can add existing NGINX instances that are already registered with NGINX One to a Config Sync Group.

0 commit comments

Comments
 (0)