Proceedings of the Third International Conference on Trends in Electronics and Informatics (ICOEI 2019)

IEEE Xplore Part Number: CFP19J32-ART; ISBN: 978-1-5386-9439-8

Docker Swarm and Kubernetes in Cloud Computing

Environment
Nikhil M arathe Ankita Gandhi Jaimeel M Shah
Computer Science and Engineering Computer Science and Engineering Computer Science and Engineering
Parul University Parul University Parul University
Vadodara, India Vadodara, India Vadodara, India
niks6nuts@gmail.com ankita.gandhi@paruluniversity.ac.in jaimeel.shah@paruluniversity.ac.in

Abstract— Distributed computing is a technology which

contributes new stack of computing placed on virtualization of
assets. With the most recent pattern of building up the
applications on cloud, which empower the customer to get to it in
an expanding way, by this the heap climbing quickly on the
servers. Due to this sense of growing the stack on the servers, the
resources are not efficiently exploited. S o this is the logic why it
has been brought in this era. The main ambition of us is to
balance the work on each & every nodes. This will help to
distribute the work on different nodes by remembering that no
hubs ought to be overloaded. Thus this paper include what is
docker and container by this clear cut ideas will helps us out to
understand the docker swarm and kubernetes technology.
Finally the paper shows how the services is been access by the
node in a cluster with the help out docker swarm and kubernetes
and also it provide the difference between them.

Keywords— Cloud Computing, Docker, Container, Docker Swarm Figure 1: Scenario of cloud computing & services [12].
and Kubernetes.

The sending model expresses the kind of access gave to the

cloud client as appeared in figure 2. Cloud comprises of four
I.INTRO DUCTIO N
organization models:-

Distributed computing advert to an application which

a. Public Cloud: This cloud grants the operations of services
conveyed the services over the web, for example, equipment
and systems comfortably by generic human being. Example is
administrations, programming administrations, on-request
Google, IBM, Amazon, Microsoft etc.
benefits, pay-per-use administrations and other assortment of
administrations in the datacenters that give those
b. Private Cloud: This cloud grants the services and systems
administrations.
to be operated inside the federation. Additionally it can handle
by third person or itself by federation.
Circulated figuring condition is a mixture of two portions: the
back end and the front end related through a virtual
c. Community Cloud: This cloud grants the services and
framework or the web. The foremost end is available to the
systems by a group of federations. It shares the framework
customer (client). The back end addresses an expert
amongst various federations from a distinct community. It
association. It includes applications and interfaces that are
may be handled by a third party or internally by a federation.
important to get to the dispersed registering stages. The
circulated registering circumstance is depict in figure 1. It
d. Hybrid Cloud: It is the composite of public and private
exhibits how the particular Cloud organizations can be gotten
cloud. Crucial activities are achieved by private cloud and
to by different customers.
uncritical activities are performed by public cloud.

Figure 2: Deployment models.

978-1-5386-9439-8/19/$31.00 ©2019 IEEE 179

Authorized licensed use limited to: Vilnius Gediminas Technical University. Downloaded on October 31,2022 at 13:52:46 UTC from IEEE Xplore. Restrictions apply.

There are three administration models which are embedded in
Distributed computing. They are as per the following:
1. Infrastructure as a Service(IaaS):
In IaaS,the purchaser is given systems, stockpiling, handling
and different othercomputing assets. IaaS empowers a
shopper or client to send and execute thesoftware. This
product incorporates OSs andapplications. The customer isn't
responsible for the cloud framework. Be that as it may, a
consumercan control the OS, stockpiling and the
deployedapps. A customer may likewise have fractional
authority over choice of systems administration parts, for
example, have firewalls.
2. Platform as a Service (PaaS):
PaaS enables theconsumers to send their applications
whichare made utilizing programming dialects andvarious
instruments onto the cloud foundation. Thecontrol that the
shopper has is like thatof IaaS.
3. Software as a Service (SaaS):
SaaS enablesthe buyer to utilize the abilities, for example,
Applications which is driven by the serviceprovider which
keeps running on the infrastructure.These applications can be
access to from different gadgets through a slight customer
interfacesuch as an internet browser like Google
Chrome,Mozilla Firefox, IE, Opera and so on. The control
that the buyer has is like that of IaaS andPaaS. Be that as it
may, the buyer may have partialcontrol over client explicit
application arrangement settings.
Figure 3: Three services models [12].
A. CONTAINER
Compartments give a standard method to bundle your
application's code, designs, and conditions into a solitary
item. Compartments share a working framework introduced
on the server and keep running as asset detached procedures,
guaranteeing fast, dependable, and predictable organizations,
paying little heed to condition.Containers offer a sensible
Authorized licensed use limited to: Vilnius Gediminas Technical University. Downloaded on October 31,2022 at 13:52:46 UTC from IEEE Xplore. Restrictions apply.
bundling component in which applications can be
disconnected from the earth in which they really run. This
decoupling permits compartment based applications to be
conveyed effectively and reliably, paying little respect to
whether the objective condition is a private server farm,
people in general cloud, or even an engineer's close to home
workstation. Containerization gives a spotless division of
worries, as designer’scentre around their application rationale
and conditions, while IT tasks groups can concentrate on
organization and the board without wasting time with
application subtleties, for example, explicit programming
adaptations and arrangements explicit to the application.
B. Docker
Docker is a product stage that enables you to manufacture,
test, and send applications rapidly. Docker bundles
programming into institutionalized units considered holders
that have everything the product needs to run including code,
libraries, runtime, framework, and devices. Utilizing Docker,
we can rapidly use and extends applications into any
environment and know your code will run.
C. Docker Swarm
A swarm is a crew of machines that are functioning Docker
and merged into a group. After that has occurred, you keep on
running the Docker directions you're utilized to, however at
this point they are executed on a bunch by a swarm
administrator. The machines in a swarm can be physical or
virtual. Subsequent to joining a swarm, they are alluded to as
hubs.
D. Kubernetes
Kubernetes is a compartment the executives innovation
created in Google lab to oversee containerized applications in
various sort of situations, for example, physical, virtual, and
cloud framework. It is an open source framework [25] which
helps in making and overseeing containerization of use.
II. BACKGROUND AND RELATED WORK
In this paper, producer portray that, it is to offer an assessment
of various hosts that can be provisioned in Open Stack. Inside
this degree, we have assessed uncovered metal hosts, VM
based hosts and Dockers holder based has the degree that
CPU, Networking, Memory, Disk I/O and boot-up times. We
moreover studied the effects of running OpenStack [14].
180
In this paper, the creator has been conveyed a vitality
convincing strategy, Hypriot Cluster Lab (HCL) that changes
Dockers moves so as to keep running on ARM fuelled single
board PCs. In this, we show how HCL works with plenitude
and replication between a couples has on various locales by
techniques for wide region systems. In like manner, we utilize
a work sort out subject to virtual private LANs to connect with
encoded correspondence over the Internet between coursed
has. Our outcome shows denounce tolerant, solid and secure
improvement to associate two or three self-decision has with
HCL to accomplish the QoS-necessities [13].
In this paper, Ironic (exposed metal) distributes the entire
server equipment to the heap. Accordingly, applications can
run locally on the host and totally utilize the shrouded gear. In
any case, this is a solitary inhabitant alternative as unused
equipment assets can't be shared or re-utilized by others inside
the server farm. Thus exposed metal will in general decline by
and large usage rates, and is frequently not a practical
alternative. Also, from an Ironic task point of view,
extraordinary augmentations are have to enable access to
equipment assets. Usage of these augmentations confines the
rundown of upheld equipment and prompts increment the
expense of creating and keeping up the OpenStack Ironic
driver.
This paper presents another virtualization innovation Docker
and clarifies standards inside and out about its center parts
including Linux namespaces and cgroups. As the foundation
in JCDB, direction of how to run MongoDB and Cassandra
examples is given in GitHub. At last, we give the conceivable
application situations which are advantageous to designing
advancement of combination gadgets.
III. METHODOLOGY
In this bit we depict the strategies which has been done and
results will be completed in assessment segment. Before we
do that we begin by giving progressively explicit definitions
to a lot of terms that are utilized widely all through this paper.
A. Docker Swarm
A swarm is a crew of machines that are functioning Docker
and merged into a group. After that has occurred, you keep on
running the Docker directions you're utilized to, however at
this point they are executed on a bunch by a swarm
administrator. The machines in a swarm can be physical or
virtual. Subsequent to joining a swarm, they are alluded to as
hubs.
Swarm directors can utilize a few methodologies to run
holders, for example, "emptiest hub" which fills the least used
machines with compartments. Or then again "worldwide",
which guarantees that each machine gets precisely one
occasion of the predetermined compartment. You train the
swarm administrator to utilize these methodologies in the
Compose record, much the same as the one you have just
been utilizing.
Swarm directors are the main machines in a swarm that can
execute your directions, or approve different machines to join
the swarm as laborers. Specialists are only there to give limit
and don't have the expert to tell whatever other machine what
it may or may not be able to.

In this paper, Cloud figuring makes broad utilization of virtual

machines since they allow remaining tasks at hand to be
detached from each other and for the asset use to be fairly
controlled. Later on, we investigate the execution of
customary virtual machine (VM) arrangements, and balance
them with the utilization of Linux holders. We use it as a
delegate hypervisor and Docker as a holder supervisor. Our
Figure 4: Swarm Cluster
outcomes demonstrate that compartments result in equivalent
or preferable execution over VMs in practically all cases. B. Kubernetes
Both VMs and compartments expect tuning to help I/O
concentrated applications.

The leftout of the areas of the paper are organized as pursues:

The Methodology segment portrays our techniques

engineering that has been performed. The Evaluation state
how it has been implemented and furthermore last outcome
appear in figures. At last, the paper completes off with the
conclusions that can be gotten from this work and a set of
further steps that can be taken as a feature of Future Work.

Figure 5: Kubernetes

181

Authorized licensed use limited to: Vilnius Gediminas Technical University. Downloaded on October 31,2022 at 13:52:46 UTC from IEEE Xplore. Restrictions apply.

Following are the components of Kubernetes.
Etcd
It stores the arrangement data which can be utilized by each
one of the hubs in the group. It is a high accessibility key
esteem store that can be disseminated among various hubs. It
is open just by Kubernetes API server as it might have some
touchy data. It is a conveyed key esteem Store which is open
to all.
API Server
Kubernetes is an API server which gives all the task on
bunch utilizing the API. Programming interface server
actualizes an interface, which implies distinctive instruments
and libraries can promptly speak with it. Kubeconfig is a
bundle alongside the server side apparatuses that can be
utilized for correspondence. It uncovered Kubernetes API.
Scheduler
This is one of the key segments of Kubernetes ace. It is an
administration in ace in charge of dispersing the remaining
task at hand. It is in charge of following us age of working
burden on group hubs and after that setting the remaining task
at hand on which assets are accessible and acknowledge the
outstanding task at hand. As it were, this is the component in
charge of apportioning cases to accessible hubs. The
scheduler is in responsible of outstanding burden usage and
allotting case to new hub.
administration account controller [23]. The controller chief
runs diverse sort of controllers to deal with hubs, endpoints,
and so on.
Kubernetes Proxy Service
This is an intermediary benefit which keeps running on every
hub and aides in making administrations accessible to the
outer host. It helps in sending the demand to address holders
and is equipped for performing crude load adjusting. It
ensures that the systems administration condition is
unsurprising and open and in the meantime it is separated
also. It oversees units on hub, volumes, privileged insights,
making new compartments' wellbeing registration, and so
forth.
IV. EVALUATION
In case of swarm cluster we consider 3 node and one of them
is master node and remaining one is slave node. First of all we
give the ip address to respective node. Secondly install the
docker and start the docker. Then after open some of the
Firewall ports. All the preceding steps we have to do in all
three node. Further we operate the commands for swarm
cluster on our Master node and then after we have to add the
slave node in it. Final launch the services on master node and
it will be available on all remaining nodes. The services as
display on figure 6, figure 7 & figure 8.

Controller Manager
This segment is responsible of the greater part of the
gatherers that manages the condition of bunch and plays out
an errand. By and large, it tends to be considered as a
daemon which keeps running in nonterminating circle and is
in charge of gathering and sending data to API server. It
progresses in the direction of getting the mutual condition of
group and after that make changes to bring the present status
of the server to the ideal state. Figure 6: Node1.

Docker
The main necessity of every hub is Docker which helps in
running the typified application holders in a generally
disengaged however lightweight working condition.
Kubelet Service
This part is in charge of a large portion of the gatherers that
directs the condition of bunch and plays out an errand. As a
rule, it tends to be considered as a daemon which keeps
Figure 7: Node2.
running in nonterminating circle and is in charge of
gathering and sending data to API server. It progresses in the
direction of getting the common condition of bunch and after
that make changes to bring the present status of the server to
the ideal state. The key controllers are replication controller,
endpoint controller, namespace controller, and

182

Authorized licensed use limited to: Vilnius Gediminas Technical University. Downloaded on October 31,2022 at 13:52:46 UTC from IEEE Xplore. Restrictions apply.
 The figure 9 & figure 10 shows the graph of cpu utilization
and memory utilization by the help of this we can say that in
terms of Cpu and memory performance Kubernetes is better
than swarm cluster.

Docker Swarm Kubernetes

Performance Decreased
Flexibility is less
It not Provide Fault tolerant
It has lack in this.
Figure 8: Node3
It is not self-healing
Performance increased
Flexibility is higher
It provide Fault Tolerant
It has built-in library and
process.
It is self-Healing

Table 1: Difference between Docker swarm and

Kubernetes.

V. CONCLUS ION
Since from previous couple of years, cloud computing has
widely been used to both the individuals and the
establishment. The technology docker and container is been
used, which would be helpful everyone in terms of load
balancing, security etc. further we had implemented the
docker swarm and kubernetes in form of cluster and run the
services on it and we got that kubernetes is superior than the
docker swarm even though kubernetes is difficult in installing
process but if it effective in major ways then installation will
be consider in a negligible manner.

VI. FUTURE WORK

Run an application on apache mesos then compare overall
performance.

Figure 9: Kubernetes Performance

VII. REFERENCES

[1] T . Deepa, Dr. Dhanaraj Cheelu,” A Comparative Study of Static and

Dynamic Load Balancing Algorithms in Cloud Computing”,
International Conference on Energy, Communication, Data Analytics
and Soft Computing (ICECDS-2017).

[2] Simranjit Kaur, T ejinder Sharma, “Efficient Load Balancing using

Improved Central Load Balancing T echnique”, Proceedings of the
Second International Conference on Invent ive Systems and Control
(ICISC 2018) IEEE Xplore Compliant - Part Number:CFP18J06-ART ,
ISBN:978-1-5386-0807-4; DVD Part Number:CFP18J06DVD,
ISBN:978-1-5386-0806-7.

[3] Sukhpreet Kaur, Dr. Jyotsna Sengupta,” Load Balancing using

Improved Genetic Algorithm (IGA) in Cloud computing”, International
Journal of Advanced Research in Computer Engineering & T echnology
(IJARCET ) Volume 6, Issue 8, August 2017, ISSN: 2278 – 1323.

[4] M.Padmavathi, Prof.Shaik. Mahaboob Basha, “Dynamic And Elasticity

ACO Load Balancing Algorithm for Cloud Computing”, International
Conference on Intelligent Computing and Control Systems ICICCS
2017.

[5] Farzana Sadia, Nusrat Jahan, Lamisha Rawshan, Madina T ul Jeb and
Dr. T ouhid Bhuiyan, “A Priority Based Dynamic Resource Mapping
Figure 10: Swarm cluster Performance Algorithm For Load Balancing In Cloud ”, Proceedings of the 2017 4th
International Conference on Advances in Electrical Engineering
The same configuration we have to do in kubernetes for (ICAEE), 28-30 September, Dhaka, Bangladesh.

launching the services like a cluster.But different between [6] Anureet kaur, Bikrampal Kaur, “Load Balancing in tasks using Honey
them is shown in Table 1. bee Behavior Algorithm in Cloud Computing”, 978-1-5090-0893-
3/16/$31.00 ©2016 IEEE.

183

Authorized licensed use limited to: Vilnius Gediminas Technical University. Downloaded on October 31,2022 at 13:52:46 UTC from IEEE Xplore. Restrictions apply.
[7] Jaimeel M Shah, Dr Sharnil Pandya, Dr Narayan Joshi, Dr Ketan
Kotecha and Dr D.B.Choksi, “Load Balancing in cloud computing:
Methodological Survey on different types of algorithm”, International
Conference on T rends in Electronics and Informatics ICEI 2017.
[8] Ms. Shalini Joshi, Dr. Uma Kumari, “Load Balancing in Cloud
Computing: Challenges&Issues”, 2016 2nd International Conference on
Contemporary Computing and Informatics (ic3i).
[9] Mahfooz Alam and Zaki Ahmad Khan, “Issues and Challenges of Load
Balancing Algorithm in Cloud Computing Environment”, Indian
Journal of Science andT echnology”,Vol10(25),
DOI:10.17485/ijst/2017/v10i25/105688, July 2017.
[10] Abhijit Aditya, Uddalak Chatterjee and Snehasis Gupta, “A
Comparative Study of Different Static and Dynamic Load Balancing
Algorithm in Cloud Computing with Special Emphasis on Time Factor
”, International Journal of Current Engineering and T echnology E-ISSN
2277 – 4106, P-ISSN 2347 – 5161 ©2015 INPRESSCO®, All Rights
Reserved Available at http://inpressco.com/category/ijcet .
[11] Mubarak Haladu and Joshua Samual, “Optimizing Task Scheduling and
Resource allocation in Cloud Data Center, using Enhanced Min-Min
Algorithm”, IOSR Journal of Computer Engineering (IOSR-JCE) e-
ISSN: 2278-0661,p-ISSN: 2278-8727, Volume 18, Issue4,Ver.VI(Jul.-
Aug.2016),PP18-25 www.iosrjournals.org.
[12] NageswararaoAngadala and G. Satyanarayana, “ Customized Cloud
Resources Using OVMP Based on SIP Servers”, 2014, IJARCSSE All
Rights Reserved.
[13] Marcel Großmann, Andreas Eiermann, “Automated Establishment of a
Secured Network for Providing aDistributed Container Cluster”, 2016
28th International T eletraffic Congress - T he First International
Conference in Networking Science & Practice.
978-1-5386-9439-8/19/$31.00 ©2019 IEEE
Authorized licensed use limited to: Vilnius Gediminas Technical University. Downloaded on October 31,2022 at 13:52:46 UTC from IEEE Xplore. Restrictions apply.
[14] CharalamposGavriilKominos, Nicolas Seyvet and
KonstantinosVandikas, “Bare-metal, Virtual Machines and Containers
in OpenStack”, IEEE 2017.
[15] Qiang Liu, Wei Zheng , Ming Zhang , Yuxing Wang, and Kexun Yu,
“Docker-Based Automatic Deployment for Nuclear Fusion
Experimental Data Archive Cluster”, 0093-3813 © 2018 IEEE.
[16] Nikhil Marathe, Ankita Gandhi and Jaimeel M Shah, “A review on
different approaches of load balancing in cloud computing”.
[17] G. J. Popek and R. P. Goldberg, “Formal requirements for virtualizable
third generation architectures,” ACM, vol. 17, no. 7, pp. 412–421, 1974.
[18] “Libvirt: The virtualization api.” [Online]. Available: http://libvirt.org/.
[19] “Under the hood with nova, libvirt and kvm,” OpenStack Summit,
2014.
[20] “Docker: Build, ship, run.” [Online]. Available:
https://www.docker.com/
[21] “Paravirtualized drivers for kvm/linux.” [Online]. Available:
http://w w w .linux-kvm.org/page/Virtio
[22] Arsh Modak1, Prof. S.D.Chaudhary2, Prof. P.S.Paygude3,
Prof.S.R.Idate, “Techniques to Secure Data on Cloud: DockerSwarm or
Kubernetes?”, 978-1-5386-1974-2/18/$31.00 ©2018 IEEE.
[23] https://www.tutorialspoint.com/kubernetes/kubernetes_architecture.htm
[24] https://docs.docker.com/get -started/part4/
https://azure.microsoft.com/en-us/blog/azure-source-volume-58/
184