Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Look into Config Drive instead of calling Metadata Service on OpenStack #4

Open
gardener-robot-ci-1 opened this issue Jan 13, 2018 · 0 comments
Open

Look into Config Drive instead of calling Metadata Service on OpenStack #4

gardener-robot-ci-1 opened this issue Jan 13, 2018 · 0 comments
Labels
component/kubify Kubify kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/openstack OpenStack platform/infrastructure status/accepted Issue was accepted as something we need to work on

Comments

@gardener-robot-ci-1
Copy link

Issue by I820491
Monday Dec 04, 2017 at 09:36 GMT
Originally opened as https://git.removed/kubernetes-attic/kubify/issues/13

Since we are facing a few problems with the metadata service on OpenStack we should consider using the Config Drive to retrieving the instance meta data. Terraform has a support for that [1]. Also it looks like the kube-controller-manager can handle this as well [2].

[1] https://www.terraform.io/docs/providers/openstack/r/compute_instance_v2.html#config_drive
[2] kubernetes/kubernetes#23733
@gardener-robot-ci-1 gardener-robot-ci-1 added the kind/enhancement Enhancement, improvement, extension label Jan 13, 2018
@afritzler afritzler added the platform/openstack OpenStack platform/infrastructure label Feb 1, 2018
@vlerenc vlerenc added the component/kubify Kubify label Jun 27, 2018
@vlerenc vlerenc added the status/accepted Issue was accepted as something we need to work on label Aug 5, 2018
@ccwienk ccwienk modified the milestones: 2018-Q4, 2018-Q3 Aug 16, 2018
@ccwienk ccwienk added status/accepted Issue was accepted as something we need to work on lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) status/new Issue is new and unprocessed and removed lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) status/accepted Issue was accepted as something we need to work on labels Aug 16, 2018
@ccwienk ccwienk modified the milestones: 2018-Q4, 2018-Q3 Aug 16, 2018
@ccwienk ccwienk added status/in-progress Issue is in progress/work status/new Issue is new and unprocessed and removed status/new Issue is new and unprocessed status/in-progress Issue is in progress/work labels Aug 16, 2018
@ccwienk ccwienk closed this as completed Aug 16, 2018
@ccwienk ccwienk added status/closed Issue is closed (either delivered or triaged) and removed status/in-progress Issue is in progress/work labels Aug 16, 2018
@ccwienk ccwienk reopened this Aug 16, 2018
@ccwienk ccwienk added status/accepted Issue was accepted as something we need to work on and removed status/closed Issue is closed (either delivered or triaged) labels Aug 16, 2018
@ccwienk ccwienk added lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) status/accepted Issue was accepted as something we need to work on and removed lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) labels Aug 16, 2018
@ccwienk ccwienk added this to the 2018-Q3 milestone Aug 17, 2018
@ccwienk ccwienk added the status/accepted Issue was accepted as something we need to work on label Aug 17, 2018
@ccwienk ccwienk removed this from the 2018-Q3 milestone Aug 17, 2018
@ccwienk ccwienk added lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) status/accepted Issue was accepted as something we need to work on and removed lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) labels Aug 17, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 18, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 18, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 17, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Apr 19, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 19, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Aug 19, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 19, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 19, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 17, 2020
@ghost ghost added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 18, 2020
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
component/kubify Kubify kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/openstack OpenStack platform/infrastructure status/accepted Issue was accepted as something we need to work on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@afritzler @vlerenc @ccwienk @gardener-robot-ci-1 @gardener-robot