but does not give a hint that this is to be constantly provided by some internal service.
On the contrary, it says
"Cloud-init is the industry standard multi-distribution method for cross-platform cloud instance initialization. It is supported across all major public cloud providers, provisioning systems for private cloud infrastructure, and bare-metal installations."
It says „instance initalization”. It does not say that is keeps modifying the living instance.
So this is undocumented behaviour, and I am more and more thinking about the question, whether this is a backdoor.
Yes, I do think this is unreasonable.
It is definitely not Hetzner's task to fix Ubuntu.
Especially since that process of re-initiialization of that instance ID is neither obvious nor documented.
Looking at
https:/ /cloudinit. readthedocs. io/
I did not yet find an explanation of what is going on, and at
https:/ /cloudinit. readthedocs. io/en/latest/ topics/ instancedata. html
it just says
v1.instance_id
Unique instance_id allocated by the cloud.
Examples output:
i-<hash>
but does not give a hint that this is to be constantly provided by some internal service.
On the contrary, it says
"Cloud-init is the industry standard multi-distribution method for cross-platform cloud instance initialization. It is supported across all major public cloud providers, provisioning systems for private cloud infrastructure, and bare-metal installations."
It says „instance initalization”. It does not say that is keeps modifying the living instance.
So this is undocumented behaviour, and I am more and more thinking about the question, whether this is a backdoor.