We recently had an issue with conflicting versions of elasticsearch and curator being deployed. This made me have a quick look into where we pull curator from, and it looks messy to me. I'm unsure of how to clean it properly, but here are the parts I understand.
- curator is required by spicerack, thus it was added to the spicerack component in reprepro (see gerrit for details).
- elastic provided packages (elasticsearch, kibana, logstash) are in specific components for each minor version (thirdparty/elastic55, thirdparty/elastic56, ...) with the appropriate configuration to pull the packages from the elastic apt repo. This allows smoother upgrade path between versions, with different components being used for the logstash and the cirrus elasticsearch clusters.
- there is still some config to pull elasticsearch-curator in main>thirdparty, but it looks outdated, it references http://packages.elastic.co instead of https://artifacts.elastic.co
It looks to me like the natural place for curator packages is in the same elastic55 / elastic56 / ... components as the rest of the packages provided by elastic.