Consider the missing APIs that are not implemented #24
Labels
enhancement
New feature or request
needs investigation
nice to have
Something nice to have but without a high priority.
Comments
matheuscscp
added
good first issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most of the APIs of the GKE Metadata Server that are not implemented yet cannot be trivially mapped in a generic Kuberntes cluster.
A few ideas:
/computeMetadata/v1/instance/hostnameand/computeMetadata/v1/instance/idcould return the same as/computeMetadata/v1/instance/name(GCE docs for/nameare here).The remaining APIs under
/computeMetadata/v1/project/and/computeMetadata/v1/instance/attributes/refer to GCP resources and concepts that may not necessarily exist in the context of a generic Kubernetes cluster. What if for those APIs there was some sort of static configuration in the emulator? Another option is retrieving this info from Node annotations.The text was updated successfully, but these errors were encountered: