New to KubeDB? Please start here.
Using private Docker registry
KubeDB operator supports using private Docker registry. This tutorial will show you how to use KubeDB to run Redis database using private Docker images.
Before You Begin
At first, you need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. If you do not already have a cluster, you can create one by using Minikube.
You will also need a docker private registry or private repository. In this tutorial we will use private repository of docker hub.
You have to push the required images from KubeDB’s Docker hub account into your private registry. For redis, push the following images to your private registry.
$ export DOCKER_REGISTRY=<your-registry>
$ docker pull kubedb/operator:0.8.0-beta.2 ; docker tag kubedb/operator:0.8.0-beta.2 $DOCKER_REGISTRY/operator:0.8.0-beta.2 ; docker push $DOCKER_REGISTRY/operator:0.8.0-beta.2
$ docker pull kubedb/redis:4 ; docker tag kubedb/redis:4 $DOCKER_REGISTRY/redis:4 ; docker push $DOCKER_REGISTRY/redis:4
Create ImagePullSecret
ImagePullSecrets is a type of a Kubernete Secret whose sole purpose is to pull private images from a Docker registry. It allows you to specify the url of the docker registry, credentials for logging in and the image name of your private docker image.
Run the following command, substituting the appropriate uppercase values to create an image pull secret for your private Docker registry:
$ kubectl create secret docker-registry myregistrykey \
--docker-server=DOCKER_REGISTRY_SERVER \
--docker-username=DOCKER_USER \
--docker-email=DOCKER_EMAIL \
--docker-password=DOCKER_PASSWORD
secret "myregistrykey" created.
If you wish to follow other ways to pull private images see official docs of kubernetes.
NB: If you are using kubectl 1.9.0, update to 1.9.1 or later to avoid this issue.
Install KubeDB operator
When installing KubeDB operator, set the flags --docker-registry and --image-pull-secret to appropriate value. Follow the steps to install KubeDB operator properly in cluster so that to points to the DOCKER_REGISTRY you wish to pull images from.
Create Demo namespace
To keep things isolated, this tutorial uses a separate namespace called demo throughout this tutorial. Run the following command to prepare your cluster for this tutorial:
$ kubectl create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0-beta.2/docs/examples/redis/demo-0.yaml
namespace "demo" created
$ kubectl get ns
NAME STATUS AGE
default Active 45m
demo Active 10s
kube-public Active 45m
kube-system Active 45m
Deploy Redis database from Private Registry
While deploying Redis from private repository, you have to add myregistrykey secret in Redis spec.imagePullSecrets.
Below is the Redis CRD object we will create.
apiVersion: kubedb.com/v1alpha1
kind: Redis
metadata:
name: redis-pvt-reg
namespace: demo
spec:
version: 4
doNotPause: true
storage:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 50Mi
imagePullSecrets:
- name: myregistrykey
Now run the command to deploy this Redis object:
$ kubedb create -f https://raw.githubusercontent.com/kubedb/cli/0.8.0-beta.2/docs/examples/redis/private-registry/demo-2.yaml
validating "https://raw.githubusercontent.com/kubedb/cli/0.8.0-beta.2/docs/examples/redis/private-registry/demo-2.yaml"
redis "redis-pvt-reg" created
To check if the images pulled successfully from the repository, see if the Redis is in running state:
$ kubectl get pods -n demo -w
NAME READY STATUS RESTARTS AGE
redis-pvt-reg-0 0/1 Pending 0 0s
redis-pvt-reg-0 0/1 Pending 0 0s
redis-pvt-reg-0 0/1 ContainerCreating 0 0s
redis-pvt-reg-0 1/1 Running 0 2m
$ kubedb get rd -n demo
NAME STATUS AGE
redis-pvt-reg Running 15s
Cleaning up
To cleanup the Kubernetes resources created by this tutorial, run:
$ kubedb delete rd,drmn -n demo --all --force
$ kubectl delete ns demo
namespace "demo" deleted
Next Steps
