Skip to content
This repository was archived by the owner on Jan 11, 2023. It is now read-only.

rationalize instance metadata story #1734

Closed
jackfrancis opened this issue Nov 8, 2017 · 1 comment · Fixed by #1763
Closed

rationalize instance metadata story #1734

jackfrancis opened this issue Nov 8, 2017 · 1 comment · Fixed by #1763
Assignees
@jackfrancis
Labels
priority/P0

Comments

@jackfrancis
Copy link
Member

Is this an ISSUE or FEATURE REQUEST? (choose one): ISSUE

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) Kubernetes

  1. Enable Kubernetes clusters to be deployed by default with instance metadata enabled (this will reduce overhead to Azure control plane API.
  2. Develop a configuration story or set of stories for instance metadata opt-in/opt-out for acs-engine use-cases.
  3. Implement above
@brendandburns
Copy link
Member

This is all already implemented. Search for the 'useInstanceMetadata' in the API model.

We just need to set it to 'true' by default (or test and then set it to true)

@jackfrancis jackfrancis self-assigned this Nov 13, 2017
@jackfrancis jackfrancis mentioned this issue Nov 13, 2017
Merged
@ghost ghost added the in progress label Nov 13, 2017
@ghost ghost removed the in progress label Nov 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jackfrancis jackfrancis

Labels
priority/P0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

enabled instance metadata service by default jackfrancis/acs-engine
2 participants
@jackfrancis @brendandburns