#general - January 2021

Hey everyone, give a warm welcome to our newest members!
- @Jeff Everett

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Yashodhan Ghadge
- @Gene Fontanilla

Good to have you here =)

Who works for slack here????? ohhh wait....

Hey everyone, give a warm welcome to our newest members!
- @Chris F
- @Adam
- @Nenad Strainovic
- @Pat M

Good to have you here =)

Hello All! 🙂 Julian here, trying to learn the latest and greatest of DevOps practices and incorporate them into my architecture for the ultimate in AWS Wizardry. 🧙‍♂️🏾

Hey everyone, give a warm welcome to our newest members!
- @Robinlemonz
- @winslow cuthbert
- @Uri Unger
- @Julian
- @Prashanth Dudipala
- @Teja
- @khabbabs
- @Ridge F

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Ron Wood
- @Andrew Drob
- @Aamir Nayeem
- @Trọng Trương
- @Bill Clark
- @charlesz

Good to have you here =)

</wave>

Hey everyone, give a warm welcome to our newest members!
- @Connor Gervin
- @Patrick Jahns
- @AdoSa
- @G Byte
- @Advait Patel

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @cole
- @Jeremy R
- @hrampur
- @Vincent Sheffer
- @Kamal Joshi

Good to have you here =)

Thanks for the welcome.

Hey everyone, give a warm welcome to our newest members!
- @Coco

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Moacy Barros
- @daniel.doan

Good to have you here =)

Miss the old scaffolding from rails etc when building grpc go apps? -- https://github.com/lileio/lile

Hey everyone, give a warm welcome to our newest members!
- @Nikita Kuprin
- @Bayrem Kaddoussi
- @Oleg Batozhnyi

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Scott Cochran
- @JT
- @davejdyer
- @Kenji Nakamura
- @Liam Helmer
- @Ankit Rathi
- @Avishay Ashkenazi
- @Vesa
- @Dmitriy Solodukha
- @Leo D'Angelo

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Gabin
- @Albert Attias
- @SA
- @RRR
- @Dennis Lipovsky
- @Tony Hirsch
- @Steve

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Gokula Santhiya R
- @Thomas Hoefkens
- @Nikolay Iks
- @Hans Westerbeek
- @Lee Wilson

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Qing Jiang
- @Sergei Kolobov
- @Pravin Singh Rajput
- @Michael Dizon
- @Oksana Chistaya
- @Justin Wehrman
- @Jon Jozwiak
- @Ashley Mooney

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Jonas Sjödin

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Zach M
- @S Bhaskar Sarma Emani

Good to have you here =)

Thank you for the welcome! 😄

Hey everyone, give a warm welcome to our newest members!
- @Corey Smith
- @Vamshi Siddarth Gaddam
- @Nathan Flynn
- @Klaus F
- @Artyom Sukharev

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Zach Holt
- @Dahs81

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Dirk.Kappel
- @Chris Farnham

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Mansoor Ebrahim
- @oskar maria grande
- @Srikar
- @Владимир Гуринович
- @rbadillo
- @Vladimir Mukhin
- @Ricardo Underwood
- @Moshe Edri

Good to have you here =)

Anyone using pritunl? Any feedback on this tool / the paid options?

I’m getting pushback from a client’s auditing team that Tailscale is not PCI compliant (still working through that with them). But just in case that doesn’t work out, I’m looking for real experience on pritunl. I feel like I’ve heard folks discuss it here before and weigh in on pros / cons, but can’t seem to find it.

Hey everyone, give a warm welcome to our newest members!
- @Adam Schepis
- @Tim Bailey-Jones
- @iontom R
- @newbieCpo
- @Lawrence Lee

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Eyal Rot

Good to have you here =)

Hi all: ever want to learn more about raw Linux networking, e.g. under the Docker level? Here's a very clear explanation of veth devices and bridging and the other machinery Docker/Kubernetes uses to route container packets to/from the network: https://iximiuz.com/en/posts/container-networking-is-simple/

Hey everyone, give a warm welcome to our newest members!
- @Markus Skallist
- @Florian Kasper

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Greg Nicol
- @Doug Lane (he/him)
- @Michael Koroteev
- @Ofek Solomon
- @David Miranda

Good to have you here =)

thanks for the welcome

Hey all. I know atmos is still in progress, but I am curious about components directory missing. No terraform or helmfile in there. Or perhaps I have answered my own question?

Hey everyone, give a warm welcome to our newest members!
- @Chris Anderla
- @johnpc
- @Pedro Antonio Bratti
- @Jeremy Rauch
- @Paquetaxo
- @Madan Kapoor

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Saurabh Hirani
- @Philip Asiala
- @Jerrod Finn
- @Thomas Picquet
- @Mahmoud

Good to have you here =)

Hi all, thanks for all you're doing to help the community. I joined the office-hours yesterday and it was quite interesting. I work on a small internal tools team and I'm trying to really focus on Devops and IaC to mature our processes. I've been looking into terraform / terragrunt all week and I've noticed something that feels strange to me that seems to be considered best practice across a number of tools and I was hoping to get some input from all of you.

I may get some of the wording wrong here but I'll try my best to be descriptive. So it seems that it's common to split things up into modules that do individual jobs, and environments which control configuration values and compositional instructions. The combination of configs and compositional work flows in the environments seems odd to me. I can see a place for having some of it in cases where you'd want them to have some different structure (maybe you want some kind of chaos service in staging but not in prod for example), but generally it would seem like you'd want to have most of your composition to be shared between environments. To make an analogy to software development that I'm more used to, we would create a feature branch, and work on it, then merge that code to staging, after it was tested there the same code would be merged to a prod branch which would deploy to prod. You'd have different settings for each env but the code would be the same. I wouldn't create a prod and staging directory in my source and try to copy my staging code to prod when I was ready for it to be deployed.

Where does this practice come from? Is there any argument against doing it? Does anyone know of any example repositories that do handle most of the composition in a shared folder and only uses prod and staging for things that would make them different? I'm mainly focused on terragrunt right now since I'm new and it seems to be a mature system with plenty of users and help but any examples would help.

Hey everyone, give a warm welcome to our newest members!
- @Evan Pitstick
- @Brad McCoy
- @Ratko Nikolovski
- @imran hussain

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Jordan Mendler
- @Stas Efremov
- @Iurii
- @Risto Treksler
- @Cotoka
- @Nathaniel Selzer
- @Lionel LONKAP
- @Joe Herman

Good to have you here =)

Hey everyone, give a warm welcome to our newest members!
- @Sergio (Cloud Posse)
- @Sarath Pantala
- @Alex Montgomery

Good to have you here =)