K
Q

Feasibility of docker Image deploying without dockerhub.com and Using in Jenkins

4/27/2018

I am trying to use kubernetes and Jenkins for my deployment of micro services developed using spring boot. When I am exploring , many Youtube videos and other documentation tutorials are using dockerhub.com as keeping published image as repository. Here I am feeling little bit doubts. I am adding here,

  1. Can I deploy docker image in kubernetes by using Jenkins docker image build without using this dockerhub.com ? Menas I don't want to share client code in a public place. So can I use Jenkins without dockerhub.com

Can anyone clarify my doubt please?

-- Jacob
jenkins
kubernetes

Similar Questions

Kubernetes create private namespace/domain (FQDNs)
salt-master not working yet error while setting up kubernetes cluster on aws ec2 instance
How does Kubernetes enforce the memory limit for a container?
Kubernetes: How to use https communication between pods

1 Answer

4/27/2018

You do need to use some registry- kubernetes needs a registry URL to be able to pull and instantiate a particular image as a container in a pod. To avoid having the images themselves be publicly accessible you have 2 options:

  • use a business account at a public registry. You can get one of these from Docker, or from other services like Google or Quay. When you push images using a business account, you get a private space in the public registry and only your account credentials can push and pull those images. In this case your Kubernetes- and your Jenkins- has to be configured with credentials derived from your account to be able to pull those private images into your cluster.
  • run a private registry in your cluster or on your non-cluster infrastructure There are many flavors of private registries, including Docker's, Atlassian's, and many others. This keeps your images entirely on your infrastructure. The tradeoff is that you have to configure and run this as a production service, and most private registries suitable for production use have a lot of moving parts for scalable image storage, indexing, backup, and so forth.
-- Jonah Benton
Source: StackOverflow