10.6. Container sync realms configuration


Find an example container sync realms configuration at etc/container-sync-realms.conf-sample in the source code repository.
The available configuration options are:
Table 10.28. Description of configuration options for [DEFAULT] in container-sync-realms.conf
Configuration option = Default value Description
mtime_check_interval = 300 No help text available for this option.
Table 10.29. Description of configuration options for [realm1] in container-sync-realms.conf
Configuration option = Default value Description
cluster_name1 = https://host1/v1/ No help text available for this option.
cluster_name2 = https://host2/v1/ No help text available for this option.
key = realm1key No help text available for this option.
key2 = realm1key2 No help text available for this option.
Table 10.30. Description of configuration options for [realm2] in container-sync-realms.conf
Configuration option = Default value Description
cluster_name3 = https://host3/v1/ No help text available for this option.
cluster_name4 = https://host4/v1/ No help text available for this option.
key = realm2key No help text available for this option.
key2 = realm2key2 No help text available for this option.

10.6.1. Sample container sync realms configuration file

# [DEFAULT]
# The number of seconds between checking the modified time of this config file
# for changes and therefore reloading it.
# mtime_check_interval = 300


# [realm1]
# key = realm1key
# key2 = realm1key2
# cluster_name1 = https://host1/v1/
# cluster_name2 = https://host2/v1/
#
# [realm2]
# key = realm2key
# key2 = realm2key2
# cluster_name3 = https://host3/v1/
# cluster_name4 = https://host4/v1/


# Each section name is the name of a sync realm. A sync realm is a set of
# clusters that have agreed to allow container syncing with each other. Realm
# names will be considered case insensitive.
#
# The key is the overall cluster-to-cluster key used in combination with the
# external users' key that they set on their containers' X-Container-Sync-Key
# metadata header values. These keys will be used to sign each request the
# container sync daemon makes and used to validate each incoming container sync
# request.
#
# The key2 is optional and is an additional key incoming requests will be
# checked against. This is so you can rotate keys if you wish; you move the
# existing key to key2 and make a new key value.
#
# Any values in the realm section whose names begin with cluster_ will indicate
# the name and endpoint of a cluster and will be used by external users in
# their containers' X-Container-Sync-To metadata header values with the format
# "realm_name/cluster_name/container_name". Realm and cluster names are
# considered case insensitive.
#
# The endpoint is what the container sync daemon will use when sending out
# requests to that cluster. Keep in mind this endpoint must be reachable by all
# container servers, since that is where the container sync daemon runs. Note
# the the endpoint ends with /v1/ and that the container sync daemon will then
# add the account/container/obj name after that.
#
# Distribute this container-sync-realms.conf file to all your proxy servers
# and container servers.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.