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

feat(gke): Handle hyperdisk balanced volumes #344

Merged
merged 4 commits into from
Nov 4, 2024
Merged

Conversation

Pokom
Copy link
Contributor

@Pokom Pokom commented Nov 1, 2024

First attempt at handling hyperdisk balanced volumes. The primary goal was to update the pricing map logic in such a way that would parse of hyperdisks balanced and include only the cost of capacity. Hyperdisk Balanced pricing is done in such a way that if you don't configure IOPS and Throughput, you use a free tier.

In the future IOPS, Throughput, and High Availability costs need to be saved and calculated as well.

First attempt at handling hyperdisk balanced volumes.
The primary goal was to update the pricing map logic in such a way that would parse of hyperdisks  balanced and include only the cost of capacity.
Hyperdisk Balanced pricing is done in such a way that if you don't configure IOPS and Throughput, you use a free tier.

In the future IOPS, Throughput, and High Availability costs need to be saved and calculated as well.
Copy link
Contributor

@jjo jjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, suggest adding a CAVEATS or Experimental section to the main README.md, to highlight current state of hyperdisk support.

pkg/google/gke/pricing_map.go Outdated Show resolved Hide resolved
@Pokom Pokom merged commit 5815152 into main Nov 4, 2024
2 checks passed
@Pokom Pokom deleted the feat/hyperdisk-support branch November 4, 2024 15:46
Pokom added a commit that referenced this pull request Nov 4, 2024
In #344, deprecated code was discovered which led to some confusion.
It wasn't clear exactly how to remove the deprecated code and ensure tests were still functioning.
1. Rename `GeneratePricingMap` to `ParseSkus`
2. Update `ParseSkus` to be a receiver method on PricingMaps
3. Update `pricingMap.Populate` to return the result of ParseSkus
4. Update pricing map tests to call ParseSkus instead
Pokom added a commit that referenced this pull request Nov 6, 2024
In #344, deprecated code was discovered which led to some confusion.
It wasn't clear exactly how to remove the deprecated code and ensure tests were still functioning.
1. Rename `GeneratePricingMap` to `ParseSkus`
2. Update `ParseSkus` to be a receiver method on PricingMaps
3. Update `pricingMap.Populate` to return the result of ParseSkus
4. Update pricing map tests to call ParseSkus instead
Pokom added a commit that referenced this pull request Nov 6, 2024
In #344, deprecated code was discovered which led to some confusion. It wasn't clear exactly how to remove the deprecated code and ensure tests were still functioning.
1. Rename `GeneratePricingMap` to `ParseSkus`
2. Update `ParseSkus` to be a receiver method on PricingMaps
3. Update `pricingMap.Populate` to return the result of ParseSkus
4. Update pricing map tests to call ParseSkus instead
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

Successfully merging this pull request may close these issues.

2 participants