What do you expect from Facebook? They make their money with advertising, of course they will exploit and capitalize everything that gets send through their channels.
Neither WhatsApp nor Facebook can read your messages or hear your calls with your friends, family, and co-workers on WhatsApp. Whatever you share, it stays between you. That’s because your personal messages are protected by end-to-end encryption. We will never weaken this security and we clearly label each chat so you know our commitment.
Well they also promised to never exchange data between WhatsApp and Facebook when they bought WhatsApp. You simply can't believe any promise Facebook (or any FAANG company for that matter) makes regarding privacy or how they protect your personal data.
This still seems ridiculous. Why did I need to keep secrets in my repo to begin with? GAE, as far as I can tell, has been the only major PaaS that hasn't offered a solution for this. It's so easy to get wrong...it contradicts one of the biggest rules of version control: keep your secrets out of your repo.
- I already use Helm to install open source software; there are already so many Charts available. So that makes it easy to also use Helm for my own apps (I use it just for templating though)
- Helm templating language is more flexible, but that can also bite you since it can become complex. With Kustomize, changing a single environment variable value in a Deployment is quite some work compared to Helm (I don’t like JSON patching)
> With Kustomize, changing a single environment variable value in a Deployment is quite some work compared to Helm (I don’t like JSON patching)
Config maps, enough said. I have a CD pipeline that writes environment variables to files, Kustomize eats them up and creates a configmap, environment variables in the deployment reference the config map, done.
Kapp as a layer on top of Kustomize is showing some progress. Ultimately Kustomize is like every other resource bundled with k8s, it’s a building block for higher level tooling.
Everything in 1 and 2 are lined up for work. Anything without clear action items requires follow-up and clearly signals non-urgency so it's in 3 which is the end of the day. And a 4 is just intentionally forgotten.
If you stick that in your github.com/username/me/README.md then it's documented behaviour.