bcrypt variable filter
Kubernetes likes to consume hashed values, e.g. for Ingress basic auth we need to provide a secret where the password is already hashed, e.g.: "admin:$apr1$QVF90yb6$JxGT0BWDpw0negAzDy3YT."
This forces us to have two variables: one for the password and the second for its hash
And that may become a problem in the future when we will update one and forget about another
In an ideal world will be so nice to just add something like #{Password | Bcrypt} as a value for a Kubernetes secret
Also, it is a good spot for other algorithms like Md5, Sha-X, ...
1
vote
