Skip to content

fix: N1C. Help users look for "out of sync" Instances in a CSG #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
May 2, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -100,6 +100,12 @@ Now that you created a Config Sync Group, you can add instances to that group. A

Any instance that joins the group afterwards inherits that configuration.

{{< note >}} If you see the following [Config Sync Group Status](#config-sync-group-status) message: **Out of Sync**:

- Review the instance details in NGINX One Console to identify any publication problems.
- After you change the configuration of the Config Sync Group, [Publish it](#publish-the-config-sync-group-configuration].
In that case, review and resolve discrepancies between the Instance and the rest of the Config Sync Group. {{< /note >}}

### Add an existing instance to a Config Sync Group {#add-an-existing-instance-to-a-config-sync-group}

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