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

Alibaba: Expand public pricing support #2449

Open
srpomeroy opened this issue Jan 12, 2024 · 3 comments · May be fixed by #2724
Open

Alibaba: Expand public pricing support #2449

srpomeroy opened this issue Jan 12, 2024 · 3 comments · May be fixed by #2724
Assignees
Labels
E3 Estimated level of Effort (1 is easiest, 4 is hardest) kubecost Relevant to Kubecost's downstream project needs-follow-up opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest)

Comments

@srpomeroy
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The current OpenCost Alibaba integration is limiting in a few different ways.

  1. Limited and hardcoded instance type support
    • Currently the instance family type ecs.c6.2xlarge is not valid or not tested completely for pricing API
    • Example of missing instance families:
      • c6
      • c7
      • c8a
      • gn6i
      • gn7i
      • hfc6
      • g8a
      • g8i
      • g8ae
      • g8y
  2. Limited and hard-coded regions
    • Example of mIssing regions:
      • cn-heyuan
      • cn-wuhan-lr
      • eu-west-1
      • me-central-1
  3. Instance feature pricing incompatibilities
    • Node pricing information not found for node with feature: ap-northeast-1::ecs.g6.xlarge::linux::optimize::cloud_essd::40::PL1

Describe the solution you'd like

  • Expand instance family support to include all available instance families dynamically.
  • Expand region support to include all available regions dynamically.
  • Expand pricing support to account for missing node feature pricing information.

Describe alternatives you've considered
??

Additional context
??

@mattray mattray added opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest) kubecost Relevant to Kubecost's downstream project E3 Estimated level of Effort (1 is easiest, 4 is hardest) and removed needs-triage needs-follow-up labels Jan 16, 2024
@mattray
Copy link
Collaborator

mattray commented Jan 16, 2024

@srpomeroy is this on behalf of a customer?

@srpomeroy
Copy link
Contributor Author

Yes

@teevans
Copy link
Member

teevans commented Apr 24, 2024

Tracking internally as BURNDOWN-410

@AjayTripathy AjayTripathy linked a pull request May 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E3 Estimated level of Effort (1 is easiest, 4 is hardest) kubecost Relevant to Kubecost's downstream project needs-follow-up opencost OpenCost issues vs. external/downstream P1 Estimated Priority (P0 is highest, P4 is lowest)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants