Set Up Cluster-Wide Authenticated Access to a Private Docker Registry

Setup the Cluster-wide Docker Registry authentication

Arrikto provides a way to setup the global authentication for private docker registry without the need of setting the docker secret for individual notebook. The following guide describes the way to setup a DaemonSet for automatically  authenticating to private Docker registry on an existing Kubernetes cluster: 

https://docs.arrikto.com/ops/privatereg.html?highlight=docker%20daemonset

Reset the password (or other auth info) for Docker Private Repo 

1) Delete the existing `private-registry-docker` DaemonSet by running:

root@rok-tools:/# cd ~/ops/deployments
root@rok-tools:~/ops/deployments# rok-deploy --delete \
>     rok/private-registry-docker/overlays/deploy

2) Now redeploy the `private-registry-docker` DaemonSet by following the below guide:

https://docs.arrikto.com/ops/privatereg.html?highlight=docker%20daemonset

Alternate approach.

Instead of deleting the previous installation of `private-registry-docker` DaemonSet , you can also use same process for upgrading the docker configuration which is used for deploying `private-registry-docker` DaemonSet  first time. Reapplying above change will  results in updating the  `secrets`  which are used by the `private-registry-docker` DaemonSet. But `private-registry-docker` DaemonSet may continue to use the old `secret`  instead of reloading the new one. 

In that scenario, you can delete the `private-registry-docker` DaemonSet pods (or scale them down to 0), then let them restart (or scale back up)  for changes to take effect,