You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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:
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
Agreement
The text was updated successfully, but these errors were encountered: