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

Design Proposal #004: Cost estimation #548

Merged
merged 2 commits into from
Mar 26, 2019
Merged

Design Proposal #004: Cost estimation #548

merged 2 commits into from
Mar 26, 2019

Conversation

Chabane
Copy link
Contributor

@Chabane Chabane commented Feb 16, 2019

Description

This is a design proposal towards #474.

@Chabane Chabane mentioned this pull request Feb 20, 2019
@errordeveloper
Copy link
Contributor

I'll take a good look at this once we finished up a couple of upgrade-related features.

@errordeveloper
Copy link
Contributor

@Chabane this is very good overall, thanks a lot! I'm going to merged this now, and we can always tweak the proposal via another PR.

Would you be keen to look into building a prototype of this? I'm happy to connect on Slack to discuss any implementation challenges and ideas!

@errordeveloper errordeveloper merged commit ab3815d into eksctl-io:master Mar 26, 2019
@Chabane Chabane deleted the proposal-004 branch March 26, 2019 09:51
@Chabane
Copy link
Contributor Author

Chabane commented Mar 26, 2019

thanks for your time!

Sure! I can start building a simple prototype but first I will analyze the existing code. After that, I will send you a message in slack to talk about an implementation.

@smrutiranjantripathy
Copy link
Contributor

Hi @Chabane ,

This is a great proposal. There are many customers who are looking for it. I would also like to help in the implementation. Where are you in the prototype phase ?

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.

4 participants