I've been working through the Elastic documentation, starting here: https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configuring-ece-tag-allocators.html
The guide walks through the setting up of Hot-Warm allocators/allocator templates.
I've configured a set of allocators, via templates, to be hot, and a set for warm, as per docs.
The intention is that new data/docs/indexes are written to the hot allocators/hosts, and a lifecycle policy will cause the movement of these indexes over to warm allocators/hosts, when certain conditions are met (e.g. older than n-days, or more than n-docs).
After completing the section in Cloud UI - the guide moves into configuring the life cycle policies in Kibana/Index Management.
In Kibana, I've created a life-cycle policy, and associated it with a test index, which I've created, but I cant find anywhere within the index life-cycle settings, or documentation, where there is any association to configuration made to my allocators and allocator templates in Cloud UI.
Furthermore, I can see the warning:
No node attributes configured in elasticsearch.yml
You can't control shard allocation without node attributes.
and looking into this - it is suggested that I need to create additional node configuration in the elasticsearch.yml - but this additional config (from what i can make out), also, doesn't appear to link back to the config I created in Cloud UI.
I've searched for similar error messages which led me here: https://stackoverflow.com/questions/60061442/elastic-search-no-node-attributes-configured-in-elasticsearch-yml-you-cant-co
This stack-overflow post suggests additional configuration, which looks separate, but similar in intent, to what I have already configured in Cloud UI, and is not mentioned in the documentation.
How does this all tie up, what are the missing bits?
Are two separate, possibly differing versions, of behaviours getting mixed up?