<p>I'm reading about Secrets but I'm not able to find the value of them to store user and password compared to Config Maps.</p>

<p>The content is not encrypted anyway and the way to handle or access a secret is exactly the same as using config maps.</p>

<p>And I think it is the same for storing certificates, I could use also ConfigMaps.</p>

<p>I only see the use for storing the credentials to access to a docker registry because it has a predefined structure understood by k8s.</p>

<p>I found this question:
<a href="https://stackoverflow.com/questions/36912372/kubernetes-secrets-vs-configmaps?rq=1">Kubernetes Secrets vs ConfigMaps</a>
But it is more than a year old, a lot of k8s versions.</p>

<p>What is the value of Secrets compared to ConfigMaps?</p>

<blockquote>
  <p>What is the value of Secrets compared to ConfigMaps?</p>
</blockquote>

<p>If you are sole user of your cluster and you issue commands as root/master/admin then, as you stated, probably minimal, but if your cluster is used by multiple users and you want to fine grain access rights using RBAC as stated in <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/" rel="noreferrer">documentation</a> then you could, for example, deny access to Secrets and alow access to ConfigMaps for particular user using RoleBindings or similar... Such user could handle settings for container without actually having access to credentials. We use such setup in our CI/CD pipeline for example.</p>
