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
{{ message }}
This repository has been archived by the owner on Apr 29, 2019. It is now read-only.
is there a way to reuse or extend your work to the setup of a staging/production server setup?
I mean I have your setup running on my dev machine via vagrant and now I want to set up a server and run your scripts and it should set up the VMs on the other server. Can you give me your opinion about what would be a good approach to do so? Or any downsides? Should I go through vagrant's options and try to get this repo running on a hypervisor that is more suited to data-center VMs? Or should I redo everything and just use parts? For bare-metal installations that'd be the only option, right?
The obvious flaw in this plan is that if you release a new version I just throw away the VMs and restart everything from scratch. So with a staging or production setup there should be a way of doing updates in a more sophisticated way.
The kubernetes repo offers a variety of different installation options. The alternative would be to use your setup during development and another more production-ready install for staging/production. But that would mean having knowledge about two different ways of setting up kubernetes which seems sub-optimal. I think the development environment should resemble production as close as possible.
What install method/infrastructure or cloud platform do you use for your production workloads? I want to make sure that I have a production setup that works best with this repo.
The text was updated successfully, but these errors were encountered:
Hello Paulo,
is there a way to reuse or extend your work to the setup of a staging/production server setup?
I mean I have your setup running on my dev machine via vagrant and now I want to set up a server and run your scripts and it should set up the VMs on the other server. Can you give me your opinion about what would be a good approach to do so? Or any downsides? Should I go through vagrant's options and try to get this repo running on a hypervisor that is more suited to data-center VMs? Or should I redo everything and just use parts? For bare-metal installations that'd be the only option, right?
The obvious flaw in this plan is that if you release a new version I just throw away the VMs and restart everything from scratch. So with a staging or production setup there should be a way of doing updates in a more sophisticated way.
The kubernetes repo offers a variety of different installation options. The alternative would be to use your setup during development and another more production-ready install for staging/production. But that would mean having knowledge about two different ways of setting up kubernetes which seems sub-optimal. I think the development environment should resemble production as close as possible.
What install method/infrastructure or cloud platform do you use for your production workloads? I want to make sure that I have a production setup that works best with this repo.
The text was updated successfully, but these errors were encountered: