Open justgotthis opened 4 years ago
Hey @justgotthis, thanks for reporting. This is a known issue (#29), but I think we can keep this one open as a feature request and the other one as bug.
Sounds good. Thanks for the heads up Mateusz.
- Luis L.
On Fri, Oct 23, 2020 at 1:13 AM Mateusz Gozdek notifications@github.com wrote:
Hey @justgotthis https://github.com/justgotthis, thanks for reporting. This is a known issue (#29 https://github.com/kinvolk/lokomotive/issues/29), but I think we can keep this one open as a feature request and the other one as bug.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kinvolk/lokomotive/issues/1121#issuecomment-714938283, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKXFFHQJXYK7VULCHDFO6LDSMENIRANCNFSM4S3XWWHA .
Currently I was planning to creating my lokomotive cluster with one master as my usage will be low and to save on costs. As my team usage increases, I would have liked to scale masters up to 3. Currently that is not possible without recreating the cluster again. This would be a useful feature to have and save on time. By running "cluster apply" and the fact that it is idempotent, it would just spin up 2 other servers instead of having to recreate the cluster from scratch.