Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: record cloud-specific quirks #94

Open
lucab opened this issue Jul 3, 2018 · 3 comments
Open

docs: record cloud-specific quirks #94

lucab opened this issue Jul 3, 2018 · 3 comments

Comments

@lucab
Copy link
Contributor

lucab commented Jul 3, 2018

Cloud providers may have specific quirks and restrictions which could result in surprising behaviors of coreos-metadata or which could require workarounds in the codebase. Those should be documented in the repository, so that we have an explicit note to reference.

The first example of this has been reported at coreos/bugs#2468 (comment).
Azure may (or may not, depending on agent version and settings) prevent non-root users to reach the metadata endpoint for security reasons. This affects how the coreos-metadata service can be run.

@lucab
Copy link
Contributor Author

lucab commented Sep 3, 2019

Additional cloud-specific quirk for OpenStack, coming from openshift/machine-config-operator#964 (comment).

As Openstack is not an homogeneous platform and the metadata component is only optional, the static Ignition platform ID is not useful there (i.e. it can't signal whether the metadata endpoint exists or not).
Thus, there is a more specific openstack-metadata provider ID for that, which is usually not baked into images kernel arguments (but can be opted-in manually).
For the same reason, [email protected] does not automatically work on OpenStack, but requires a custom drop-in setting ${AFTERBURN_OPT_PROVIDER} and ConditionKernelCommandLine.

@prestist
Copy link
Contributor

This falls into a similar situation => #138

@bgilbert
Copy link
Contributor

The OpenStack one is no longer relevant since #462, though CloudStack has similar behavior (#856).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants