When starting with this journey, each container cluster had its dedicated repository, with multiple branches. Each branch in these repositories had its pipeline for configuring the application. A shared configuration repository was maintained, featuring various branches to override configurations based on environmental or geographical factors.
Adidas transitioned its strategy from a push mode, where one system pushes configuration to another, to a pull mode, where the system retrieves configuration from a configuration repository.
With the global expansion of the container platform and the diverse internal clients operating in multiple execution environments, Adidas embraced a layered approach. The initial layer encompasses settings applicable across all clusters, termed the Global configuration.
[
add
]
[
|
|
...
]