Disclosure: I built the free Base64 Encoder on base64decodetool.com, and I used it for the checks in this post. Every value below is made up. None of them is a real credential.
Sooner or later someone on the team opens a Kubernetes Secret, sees a value like Tm90QVJlYWxQYXNzLTIwMjYh , and decides it looks safe enough to paste into a ticket. It isn't. That string is just a password re-encoded in a public 64-character alphabet. Anyone can turn it back in a second, with no key.
This post walks through one made-up Secret from start to finish. It shows exactly what Base64 does and doesn't do, and it covers the few habits that actually protect the value.
Encoding vs hashing vs encryption, in one table
Reversible? Needs a key?β¦