starlingx/docs
Code Issues Proposed changes
docs/doc/source/admintasks/kubernetes-admin-tutorials-authentication-and-authorization.rst
Juanita-Balaraj 0c4aa91ca4 Updated Patch Set 5 to include review comments 
Changed name of file to:
admin-application-commands-and-helm-overrides.rst

Updated Strings.txt

Updated formatting issues:
installing-and-running-cpu-manager-for-kubernetes.rst

Updated Patch Set 4 to include review comments

Admin Tasks Updated

Changed name of include file to:
isolating-cpu-cores-to-enhance-application-performance.rest

Change-Id: I0b354dda3c7f66da3a5d430839b5007a6a19cfad
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Signed-off-by: Stone <ronald.stone@windriver.com>
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
2021-01-11 23:40:36 -05:00

1.3 KiB
Raw Blame History

Authentication and Authorization

Authentication is enabled for the local Docker registry. When logging in, users are authenticated using their platform keystone credentials.

For example:

$ docker login registry.local:9001 -u <keystoneUserName> -p <keystonePassword>

An authorized administrator can perform any Docker action, while regular users can only interact with their own repositories (i.e. registry.local:9001/<keystoneUserName>/). For example, only admin and testuser accounts can push to or pull from registry.local:9001/testuser/busybox:latest

Username and Docker compatibility

Repository names in Docker registry paths must be lower case. For this reason, a keystone user must exist that consists of all lower case characters. For example, the user testuser is correct in the following URL, while testUser would result in an error:

registry.local:9001/testuser/busybox:latest

For more information about Docker commands, see https://docs.docker.com/engine/reference/commandline/docker/.