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

Add persistent storage implementation for Shoot clusters #108

Open
invidian opened this issue Jan 27, 2021 · 7 comments
Open

Add persistent storage implementation for Shoot clusters #108

invidian opened this issue Jan 27, 2021 · 7 comments
Assignees
Labels
area/storage Storage related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/equinix-metal Equinix Metal platform/infrastructure (previously Packet) priority/3 Priority (lower number equals higher priority)

Comments

@invidian
Copy link
Contributor

How to categorize this issue?

/area storage
/kind enhancement
/priority normal
/platform equinix-metal

What would you like to be added:

Extension should optionally provide an implementation to provider persistence to Shoot clusters, which should utilize EM devices disks. Previously, there was Packet CSI, however it has been removed in #103.

Why is this needed:

In order to use "shooted seeds" functionality on EM, Shoot clusters must have storage available. Other Gardener extensions like AWS, GCP or Azure supports storage out of the box, so should we.

@invidian invidian added the kind/enhancement Enhancement, improvement, extension label Jan 27, 2021
@gardener-robot gardener-robot added area/storage Storage related platform/equinix-metal Equinix Metal platform/infrastructure (previously Packet) priority/normal labels Jan 27, 2021
@gardener-robot gardener-robot added priority/3 Priority (lower number equals higher priority) and removed priority/normal labels Mar 8, 2021
@gardener-ci-robot
Copy link

The Gardener project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close

/lifecycle stale

@gardener-robot
Copy link

@gardener-ci-robot Command /add is not available to you but only to a Maintainer, Member, Author.

@deitch
Copy link
Collaborator

deitch commented Feb 9, 2022

/remove-lifecycle stale

@gardener-robot
Copy link

@deitch Command /remove-lifecycle is not known.

@deitch
Copy link
Collaborator

deitch commented Feb 9, 2022

/remove-lifecycle stale

@gardener-robot
Copy link

@deitch Command /remove-lifecycle is not known.

@deitch
Copy link
Collaborator

deitch commented Feb 9, 2022

@invidian @rfranzke is there an issue with the bot? I used the command it recommended and yet it says it does not know it.

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Aug 9, 2022
@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 Feb 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage Storage related kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage) platform/equinix-metal Equinix Metal platform/infrastructure (previously Packet) priority/3 Priority (lower number equals higher priority)
Projects
None yet
4 participants