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

Support tier0 and tier5k as storage type #587

Open
yussufsh opened this issue Feb 22, 2024 · 4 comments
Open

Support tier0 and tier5k as storage type #587

yussufsh opened this issue Feb 22, 2024 · 4 comments
Assignees

Comments

@yussufsh
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We are unable to use the below new storage types due to hard validation:

tier0    Tier0 - 25 iops/gb
tier5k   Tier5k - 5000 fixed iops

Describe the solution you'd like in detail
Disk creation should not fail with invalid PowerVS VolumeType tier5k error message when using the new storage type.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
List of storage types available: https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-about-virtual-server#storage-tiers

o/p via CLI:

# ibmcloud pi storage-types
Listing storage types in region tok04...
Type     Description
tier0    Tier0 - 25 iops/gb
tier1    Tier1 - 10 iops/gb
tier3    Tier3 - 3 iops/gb
tier5k   Tier5k - 5000 fixed iops
@yussufsh yussufsh changed the title Support tier0 and tier5k as storage Support tier0 and tier5k as storage type Feb 22, 2024
@yussufsh yussufsh self-assigned this Feb 22, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2024
@yussufsh
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 22, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 20, 2024
@mkumatag
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants