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

[Feature Proposal]: Provide a command to get the different values provided by the cloud provider #36

Open
1 of 4 tasks
dipankardas011 opened this issue Dec 7, 2024 · 3 comments

Comments

@dipankardas011
Copy link
Member

Purpose

No response

Feature Name

Command which can give cloud provider configurations

Feature Description

Need a subcommand for each cloud provider on what all regions, vm types ... are expected by the cloud provider

Benefits

It will reduce the time on finding what all vms_types, regions are available for them to utilize just one command like

ksctl get-meta --provider="^(civo|azure|aws)$"

We already have the methods for each cloud provider just need to expose them

also we can utilize this to help them get the cost for each configurations would cost them
if they are going with it
For example:

ksctl estimations cost

it will ask them couple of the questions from cloud provider then, region, cluster configuration lie vm_type and the number of them,...

by this we can use the above meta with more details to get a feel of unified way to get the cost before they start making anything also we can get these data for AKS, EKS by being optimistic

Potential Drawbacks

No response

Alternatives Considered

No response

Scope of changes

  • Cli
  • UI
  • Docs

Agreement

  • I agree to engage in constructive discussion and follow the Contribution Guidelines.
@dipankardas011
Copy link
Member Author

We will need changes on the ksctl core and the cli

@dipankardas011
Copy link
Member Author

@ksctl/maintainers-for-core is anyone interested to work?

@dipankardas011
Copy link
Member Author

🚨 Updates

Complete Solution will be implemented once the repo restructing and all the components are in place then we can added this feature. So for now we can create a release and fix stuff once done we will add it next to next release

@dipankardas011 dipankardas011 moved this from In progress to Backlog in ksctl repo Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants