This is known behavior, and expected.
cloud-init uses the metadata service to tell it if it is a new instance (and should run per-instance things).
That does create a dependency on the metadata service.
That said, I had hoped that we improved this under bug 1712680.
This is known behavior, and expected.
cloud-init uses the metadata service to tell it if it is a new instance (and should run per-instance things).
That does create a dependency on the metadata service.
That said, I had hoped that we improved this under bug 1712680.