The dockercfg secret contains the value of one of the tokens (which is required to exist in order for the service account token to continue to be a valid credential) in dockercfg format
This has been a source of confusion. I understand the need for a separate dockercfg SA that references an actual token, but why the second token? It's seems unnecessary and users don't know which one to use, why it's there, etc.
On Thu, Dec 1, 2016 at 4:59 PM, Srinivas Naga Kotaru (skotaru) <skotaru cisco com> wrote:
For Docker login purpose, I could see another token ( I think this is what you are talking about)
On Thu, Dec 1, 2016 at 3:02 PM, Srinivas Naga Kotaru (skotaru) <skotaru cisco com> wrote:
I knew we can create a service account per project and can be used as a password less API work and automations activities. Can we create a service
account at cluster level and can be used for platform operations (monitoring, automation, shared account for operation teams)?