@iximiuz I can think of kube-janitor (great of PR deployments): https://t.co/e5D0oixIGV sealed secrets: https://t.co/OfAEjrMN0k and kured: https://t.co/S5kGC136XE
@xahteiwi Regardless of where you pull from, pining images to a specific tag (or better hash) helps to make things repeatable. Also preloaded images can be useful to avoid depency on registry
@mitchellh @formalbeer ignore_changes makes this a little easier. You "terraform import" your resources, ignore_changes most attributes to get "no changes, infrastructure up to date". Then you fill in the blanks step by step, you can even collaborate if you use remote backend like Terraform Cloud
@MaartjeME I was the only one dropping the kids to school by bike this whole week. I love cycling in the snow βοΈ. It's not as slippery as people think!
@alexellisuk@arkadius@k33g_org@dnsmichi The GitLab seat-link feature is pretty cool for dynamic/per month billing. If you don't want the automatic reporting you can also report the info manually at yearly renewal. I suppose you would have a claim in the license JWT to allow/block it? https://t.co/iehKweYrdM
After talking with many members of the community and considering the safety of everyone, weβve made the difficult decision to postpone #KubeCon + #CloudNativeCon Amsterdam to July/August 2020. Details and FAQ at https://t.co/gNoBwz3vrb
@glenathan@atmarc@patrickdebois@fs111 You're right it doesn't help with the security of the build tool chain, only reduces the attack surface of the runtime image