Callout - Lists
-
Using an instance’s configuration for the group configuration: If an instance is the first to join a config sync group and the group’s configuration hasn’t been defined, the instance’s configuration will become the group’s configuration. Any instances added later will automatically inherit this configuration.
If you add multiple instances to a single config sync group, simultaneously (with automation), follow these steps. Your instances will inherit your desired configuration:
- Create a config sync group.
- Add a configuration to the config sync group, so all instances inherit it.
- Add the instances in a separate operation.
Your instances should synchronize with your desired configuration within 30 seconds.
-
Using an instance’s configuration for the group configuration: If an instance is the first to join a config sync group and the group’s configuration hasn’t been defined, the instance’s configuration will become the group’s configuration. Any instances added later will automatically inherit this configuration.
If you add multiple instances to a single config sync group, simultaneously (with automation), follow these steps. Your instances will inherit your desired configuration:
- Create a config sync group.
- Add a configuration to the config sync group, so all instances inherit it.
- Add the instances in a separate operation.
Your instances should synchronize with your desired configuration within 30 seconds.
-
Open the JSON Web Token file you downloaded from MyF5 and copy its contents.
Make sure there are no extra characters or spaces when copying the contents of the JWT token: they can invalidate the token and cause 401 errors during authentication. -
Log in to the Docker registry using the contents of the JSON Web Token file:
docker login private-registry.nginx.com --username=<JWT_CONTENTS> --password=none