#gitops - March 2020 | Slack Archive

Thomas Burtonover 6 years ago

Hello all
Have a scenario I’d love some input with. We run around 18 microservices, a mixture of frontends and backends. As with many companies we have ended up with the monolithic microservice architecture and thus we often need to release things at the same time to prevent downtime on production. We have now successfully implemented FluxCD on our staging namespace. We have two more namespaces/environments, sandbox and production. We have not yet implemented flux in these namespaces. The issue we have to now is how best to implement flux and promote services from stage>sandbox>prod. It has been suggested we could use develop and master branches. If anyone could expand on that or add anything I’d be super grateful. Hope you all have a great day

Erik Osterman (Cloud Posse)over 6 years ago

Adding @U010XGY9B46 bot

sheldonhover 6 years ago

Trying to find docs on this....

if I want to apply actions, templates, settings or anything across all my org in github, isn't there a .github special repository you can create and all the child repositories inherit this, for instance with CODE_OWNERS for example? I thought there was a special repo for github that allowed this, like the .github name or something (not the folder in each github, I'm aware of that one)