FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR AUTOMATING A CONTAINER ORCHESTRATION DEPLOYMENT”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR AUTOMATING A CONTAINER ORCHESTRATION DEPLOYMENT
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to container orchestration. More particularly, embodiments of the present disclosure relate to methods and systems for automating a container orchestration deployment.
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Container Orchestration System (COS) such as, but not limited to, Kubernetes (K8), open shift and the like, is a distributed system that runs across multiple nodes in a cluster. COS coordinates scheduling and execution of containerized applications, manages networking, storage, and other resources. Setting up and configuring the distributed system such as the COS requires knowledge of various components, their interactions, and proper configuration.
[0004] Cloud installer systems combine all the necessary steps into a single operation, abstract away all complexities and provides an automated solution for the streamlined creation of a multi control plane automated container orchestration system, thus simplifying the intricate process involved.

[0005] Further, over the period of time, various solutions have been developed to improve automated container orchestration system deployment and to provide an automated solution for the streamlined creation of a multi control plane automated container orchestration system. However, there are certain challenges with existing solutions. The existing solutions for the present disclosure require manual intervention for the setting up and configuration of the distributed system which is a time-consuming, intricate, and error-prone solution.
[0006] Thus, there exists an imperative need in the art to provide the automated container orchestration system deployment to provide an automated solution for the streamlined creation of a multi control plane automated container orchestration system, which the present disclosure aims to address.
SUMMARY
[0007] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure relates to a method for automating a container orchestration deployment, the method comprising receiving, by a transceiver unit, a deployment plan comprising at least an input login credentials associated with a set of nodes. The method further comprises validating, by a validation unit, at least one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules. Thereafter, the method comprises initiating, by a deployment unit, a predetermined deployment based on the validation of the at least one of the reachability parameters and the input login credentials. The method thereafter comprises automating, by the deployment unit, the container orchestration deployment based on the predetermined deployment.

[0009] In an exemplary aspect of the present disclosure, each of the set of nodes comprises at least one of one or more master nodes, one or more worker nodes, and one or more load balancer nodes.
[0010] In an exemplary aspect of the present disclosure, the method further comprises configuring by the deployment unit at an Automated Cloud Installer (ACI) at least one of a secured shell internet protocols (SSH IPs) associated with the one or more master nodes, a SSH IPs associated with the one or more worker nodes, a SSH IPs associated with the one or more load balancer nodes, and a Virtual IP associated with the one or more load balancer nodes based on a user input.
[0011] In an exemplary aspect of the present disclosure, initiating by the deployment unit the predetermined deployment further comprises identifying, by the deployment unit via the ACI, a successful login associated set of nodes based on the input login credentials. Further, re-configuring, by the deployment unit, one or more preconfigured configurations associated with the at least the one or more master nodes and the one or more worker nodes based on the successful login. The method further comprises, deploying, by the deployment unit, the one or more load balancer nodes based on reconfiguring the one or more preconfigured configurations. Furthermore, installing, by the deployment unit, a set of tool packages at least at the one or more master nodes and the one or more worker nodes based on deploying the one or more load balancer nodes. Further, the method comprises initiating, by the deployment unit, a set of commands based on installing the set of tool packages. Moreover, the method comprises generating, by the deployment unit, a set of logs based on at least the set of commands, and transmitting, by the transceiver unit via a user interface, the set of logs based on at least the set of commands.

[0012] In an exemplary aspect of the present disclosure, the predetermined deployment is a Kubernetes deployment to automate the container orchestration deployment.
[0013] Another aspect of the present disclosure relates to a system for automating a container orchestration deployment, the system comprising a transceiver unit configured to receive, a deployment plan comprising at least an input login credentials associated with a set of nodes. The system comprises a validation unit connected to at least the transceiver unit, the validation unit is configured to validate at least one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules. The system comprises a deployment unit connected to at least the validation unit, the deployment unit is configured to initiate a predetermined deployment based on the validation of the at least one of the reachability parameter and the input login credentials, and automate, the container orchestration deployment based on the predetermined deployment.
[0014] Yet another aspect of the present disclosure relates to a non-transitory computer readable storage medium storing instructions for automating a container orchestration deployment, the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit, of the system, to receive a deployment plan comprising at least an input login credentials associated with a set of nodes. Further, the instructions include executable code which, when executed causes a validation unit, of the system, to validate at least one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules. Further, the instructions include executable code which, when executed causes a deployment unit, of the system, to initiate a predetermined deployment based on the validation of the at least one of the reachability parameter and the input login credentials. Further, the instructions include executable code which, when executed

causes the deployment unit to automate, the container orchestration deployment based on the predetermined deployment.
OBJECTS OF THE DISCLOSURE
[0015] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0016] It is an object of the present disclosure to provide a system and a method for automating a container orchestration deployment.
[0017] It is an object of the present disclosure to provide a system and a method for automated container orchestration system deployment to provide an automated solution for the streamlined creation of a multi control plane automated container orchestration system.
DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.

[0019] FIG. 1 illustrates an exemplary block diagram [100] of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0020] FIG. 2 illustrates an exemplary block diagram of a system [200] for automating a container orchestration deployment, in accordance with exemplary implementations of the present disclosure.
[0021] FIG. 3 illustrates a method flow diagram [300] for automating a container orchestration deployment, in accordance with exemplary implementations of the present disclosure.
[0022] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0023] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0024] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and

arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0025] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0026] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0027] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.

[0028] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
5 of microprocessors, one or more microprocessors in association with a Digital
Signal Processing (DSP) core, a controller, a microcontroller, Application Specific
Integrated Circuits, Field Programmable Gate Array circuits, any other type of
integrated circuits, etc. The processor may perform signal coding data processing,
input/output processing, and/or any other functionality that enables the working of
10 the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[0029] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”,
15 “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant,
20 tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
25 [0030] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other
30 types of machine-accessible storage media. The storage unit stores at least the data
9

that may be required by one or more units of the system to perform their respective functions.
[0031] As used herein “interface” or “user interface refers to a shared boundary
5 across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
10
[0032] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more
15 microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0033] Container orchestration refers to the automated arrangement, coordination,
20 and management of containerized applications. It involves deploying, scaling, and
operating application containers across a cluster of machines.
[0034] Container Orchestration System (COS) is a platform that automates the
management, scaling, networking, and availability of containerized applications.
25 The COS is deployed in an automated manner to manage and orchestrate containers
across multiple nodes.
[0035] Kubernetes is a distributed system that runs across multiple nodes in a
cluster. It coordinates the scheduling and execution of containerized applications,
30 manages networking, storage, and other resources. Setting up and configuring a
10

distributed system requires knowledge of various components, their interactions, and proper configuration.
[0036] ACI (Automated Cloud Installer) combines all the necessary steps into a
5 single operation, abstract away all complexities and provides an automated solution
for the streamlined creation of a multi control plane Kubernetes cluster, simplifying the intricate process involved.
[0037] SSH (Secure Shell) Internet Protocols refer to the use of SSH for secure
10 communication over the internet or internal networks. SSH provides encrypted
channels for executing commands on remote machines, transferring files, and managing network services securely.
[0038] As used herein the transceiver unit include at least one receiver and at least
15 one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system and/or connected with the system.
[0039] As discussed in the background section, the current known solutions for
20 automated container orchestration system deployment to provide an automated
solution for the streamlined creation of a multi control plane automated container
orchestration system have several shortcomings. The existing solutions utilize
manual setting up and configuration of the distributed system which is a time-
consuming, intricate, and error-prone solution. The implementation of automated
25 Kubernetes cluster creation will greatly accelerate the deployment of network
functions within our infrastructure.
[0040] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing an automated solution
30 for configuring all pre-requisite configurations by a user such as, but not limited to,
secured shell (SSH) IPs of Master nodes, Worker nodes and Load Balancer nodes,
11

Virtual Internet Protocol (VIP) on Load Balancer (LB) nodes in GUI; creating a
deployment plan for deploying the COS at a Graphical User Interface (GUI) for all
the Master nodes, Worker nodes and LB nodes. The worker nodes are part of the
deployment plan and are configured and managed automatically during the
5 deployment process and the LB nodes are included in the automated deployment
plan, ensuring they are properly configured to balance the load across the worker
nodes; initiating the deployment of the COS; Logging to all nodes by the GUI once
the user initiates deployment; ensuring by the GUI that LB containers are
successfully deployed and running; installing packages by the GUI; running
10 commands to ensure that the COS is successfully deployed and ready to work; and
writing script logs to local file (on deployment host) and send real time logs to GUI.
[0041] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
15
[0042] FIG. 1 illustrates an exemplary block diagram of a computing device [100] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [100] may also implement a method for
20 automating a container orchestration deployment utilising the system. In another
implementation, the computing device [100] itself implements the method for automating a container orchestration deployment using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
25
[0043] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware processor [104] may be, for example, a general-purpose microprocessor. The
30 computing device [100] may also include a main memory [106], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [102]
12

for storing information and instructions to be executed by the processor [104]. The
main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [104]. Such instructions, when stored in non-transitory storage media
5 accessible to the processor [104], render the computing device [100] into a special-
purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
10
[0044] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
15 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor [104]. Another type of user input device may be a cursor controller [116], such as a
20 mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [104], and for controlling cursor movement on the display [112]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
25
[0045] The computing device [100] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine.
30 According to one implementation, the techniques herein are performed by the
computing device [100] in response to the processor [104] executing one or more
13

sequences of one or more instructions contained in the main memory [106]. Such
instructions may be read into the main memory [106] from another storage medium,
such as the storage device [110]. Execution of the sequences of instructions
contained in the main memory [106] causes the processor [104] to perform the
5 process steps described herein. In alternative implementations of the present
disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0046] The computing device [100] also may include a communication interface
10 [118] coupled to the bus [102]. The communication interface [118] provides a two-
way data communication coupling to a network link [120] that is connected to a
local network [122]. For example, the communication interface [118] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
15 telephone line. As another example, the communication interface [118] may be a
local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [118] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
20 various types of information.
[0047] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the communication interface [118]. In the Internet example, a server [130] might
25 transmit a requested code for an application program through the Internet [128], the
ISP [126], the local network [122], the host [124] and the communication interface [118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
30
14

[0048] Referring to FIG. 2, an exemplary block diagram of a system [200] for
automating a container orchestration deployment, is shown, in accordance with the
exemplary implementations of the present disclosure. The system [200] comprises
at least one transceiver unit [201], at least one validation unit [203], at least one
5 deployment unit [205] and at least one storage unit [207]. Also, all of the
components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system [200] should also be assumed to be connected to each other. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise
10 multiple such units or the system [200] may comprise any such numbers of said
units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user device/ user equipment [102] to implement the features of the present disclosure. The system [200] may be a part of the user device or may be independent of but in communication with the
15 user device (may also referred herein as a UE). In another implementation, the
system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
20 [0049] The system [200] is configured for automating a container orchestration
deployment, with the help of the interconnection between the components/units of the system [200].
[0050] The system [200] comprises a transceiver unit [201]. The transceiver unit
25 [201] is configured to receive a deployment plan comprising at least an input login
credentials associated with a set of nodes. This deployment plan refers to a detailed
set of instructions and configurations received by the transceiver unit [201] and the
deployment plan contains input login credentials associated with a set of nodes
within the system. Further, each of the set of nodes may include at least one of one
30 or more master nodes, one or more worker nodes, and one or more load balancer
15

nodes. Each node in the system plays a specific role in managing, processing, or distributing tasks and resources.
[0051] The system further comprises a validation unit [203] connected to at least
5 the transceiver unit [201], the validation unit [203] is configured to validate at least
one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules. The present disclosure encompasses that the validation unit [203] is responsible for checking the accuracy and functionality of certain parameters before the system is
10 fully deployed or operational. It ensures that each node in the set of nodes can be
accessed or contacted. The reachability parameter refers to a measure or criterion used to determine whether a network component (such as a node) is reachable over the network. This parameter might involve checking network connectivity, response times, or other indicators. This might involve checking network connectivity to
15 confirm that each node can communicate with the others as required and verifies
that the login credentials provided for each node are correct and can be used to successfully log into each node. The predefined validation rules may include a set of pre-defined criteria to validate various aspects of the container orchestration deployment. Examples of such pre-defined criteria may include, but are not limited
20 to, rules to verify the integrity of the deployment configuration, checking
compliance with security policies and configuring resource allocation limits. However, it may be noted that such pre-defined criteria as mentioned above are only exemplary, and in no manner to be construed to limit the scope of the present subject matter in any manner. Any other examples of pre-defined criteria may also be used,
25 and would lie within the scope of the present subject matter.
[0052] The system further comprises a deployment unit [205] connected to at least
the validation unit [203], the deployment unit [205] is configured to initiate a
predetermined deployment based on the validation of the at least one of the
30 reachability parameter and the input login credentials and automate, the container
orchestration deployment based on the predetermined deployment. The present
16

disclosure encompasses that the deployment unit [205] waits for a signal from the
validation unit [203] indicating that the reachability of nodes and the validity of
login credentials have been confirmed according to predefined rules. The
deployment unit [205] has two main functions:
5 • Initiate Predetermined Deployment: Once the validation unit [203] confirms
that the reachability parameters and input login credentials are valid, the
deployment unit [205] begins the deployment process as specified in the
deployment plan. The predetermined deployment refers to a deployment
process that follows a predefined and automated sequence of steps and
10 configurations.
• Automate Container Orchestration Deployment: The deployment unit [205] automates the setup and management of containerized applications, using a predetermined deployment method.
15 [0053] In one example, the predetermined deployment may be a Kubernetes
deployment to automate the container orchestration deployment. The term automation refers to the process where the deployment unit [205] carries out the deployment tasks without manual intervention. This involves using predetermined deployment related data, such as configuration files, deployment scripts, and
20 environment settings.
[0054] The deployment unit [205] is further configured to configure, at an Automated Cloud Installer (ACI), at least one of a secured shell internet protocols (SSH IPs) associated with the one or more master nodes, the SSH IPs associated
25 with the one or more worker nodes, the SSH IPs associated with the one or more
load balancer nodes, and a Virtual IP associated with the one or more load balancer nodes based on a user input. The present disclosure encompasses that the ACI is a tool or a platform that automates the deployment of cloud infrastructure and services. It sets up process by handling complex configurations automatically. The
30 deployment unit [205] configures the SSH IP addresses for the master nodes. These
IP addresses are used to securely access and manage the master nodes over the
17

network. Similarly, the deployment unit [205] configures the SSH IP addresses for
the worker nodes, and load balancer nodes. The deployment unit [205] configures
a Virtual IP (VIP) for the load balancer nodes. The VIP is a single IP address that
can represent a group of load balancer nodes, providing a consistent endpoint for
5 distributing traffic across multiple nodes. The configurations for SSH IPs and the
VIP are based on user input, this means that the user provides the necessary information or preferences, and the deployment unit [205] uses this input to set up the IP addresses accordingly.
10 [0055] Further, for initiation of the predetermined deployment, the deployment unit
[205] is further configured to identify, via the ACI, a successful login associated set of nodes based on the input login credentials. The deployment unit [205] re-configure, one or more preconfigured configurations associated with the at least the one or more master nodes and the one or more worker nodes based on the successful
15 login, deploy, the one or more load balancer nodes based on reconfiguring the one
or more preconfigured configurations. The deployment unit [205] is further configured to install, a set of tool packages at least at the one or more master nodes and the one or more worker nodes based on deploying the one or more load balancer nodes. Further, the deployment unit [205] initiate, a set of commands based on
20 installing the set of tool packages, generate, a set of logs based on at least the set of
commands, and the transceiver unit [201] is further configured to transmit, via a user interface, the set of logs based on at least the set of commands. The deployment unit [205] verifies that the input login credentials work for each node (master, worker, load balancer) by attempting to log in via the ACI. After successfully
25 logging in, the deployment unit [205] reconfigures existing settings or
configurations on the master and worker nodes as needed to prepare them for deployment. Using the reconfigured settings, the deployment unit [205] deploys the load balancer nodes to manage network traffic and distribute workloads. Once the load balancer nodes are deployed, the deployment unit [205] installs necessary tool
30 packages (like kubectl, kubeadm, kubelet, kubernetes-cni and cri-tools) on the
master and worker nodes. These tools in an example may include monitoring
18

agents, security tools, or other utilities required for operation. With the tool
packages installed, the deployment unit [205] executes a set of predefined
commands to further configure the system, start services, or perform other tasks
needed to finalize the deployment. During the execution of commands, the
5 deployment unit [205] runs kubeadm init and kubeadm join command to ensure
kubernetes cluster is successfully deployed and ready to work. The kubeadm init command is a Kubernetes command-line tool used to initialize a new Kubernetes control plane. Further, kubectl is the command line tool used to interact with Kubernetes clusters. The kubectl allows users to manage and deploy applications,
10 inspect, and manage cluster resources, and view logs. The kubeadm is a tool that
simplifies the process of setting up a Kubernetes cluster. The kubernetescni (Container Network Interface) is a set of standards and libraries used for configuring networking interfaces in Linux containers. The cri-tools are a set of command line tools used to interact with the Container Runtime Interface (CRI) of
15 Kubernetes.
[0056] It may be noted that the above-mentioned commands are only exemplary
and in no manner to be construed to limit the scope of the present subject matter in
any manner. Other types of commands may also be used by the deployment unit
20 [205] and would lie within the scope of the present subject matter.
[0057] When executed, it sets up the necessary components and configurations to create a functional Kubernetes cluster. The deployment unit [205] then generates logs that capture the output and status of these operations. These logs are the records
25 of events and actions taken during the deployment and operation of containers. For
example: container logs showing output from running applications, the orchestration logs detailing actions taken by the orchestration tool, etc. The ACI also writes script logs of above steps to local file (on deployment host) and send real time logs to GUI. These logs will provide valuable information for
30 troubleshooting and resolving any server-level issues that may arise. Further, the
transceiver unit [201] then transmits these logs to the user through a user interface,
19

providing feedback on the deployment status and any issues that may have occurred.
[0058] The storage unit [207] is configured to store data and instructions associated
5 with implementation of the features of the present invention.
[0059] Referring to FIG. 3, an exemplary method flow diagram [300] for
automating a container orchestration deployment, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the
10 method [300] is performed by the system [200]. Further, in an implementation, the
system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 3, the method [300] starts at step [302].
[0060] At step 304, the method comprises, receiving, by a transceiver unit [201], a
15 deployment plan comprising at least an input login credentials associated with a set
of nodes. The present disclosure encompasses that the transceiver unit [201] is designed to receive a deployment plan. This deployment plan refers to a detailed set of instructions and configurations received by the transceiver unit [201] and the deployment plan contains input login credentials associated with a set of nodes
20 within the system wherein each of the set of nodes comprises at least one of one or
more master nodes, one or more worker nodes, and one or more load balancer nodes. The set of nodes can include various types, such as master nodes, worker nodes, and load balancer nodes. Each node in the system plays a specific role in managing, processing, or distributing tasks and resources.
25
[0061] At step 306, the method comprises, validating, by a validation unit [203], at least one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules. The present disclosure encompasses the validation unit [203] is responsible
30 for checking the accuracy and functionality of certain parameters before the system
is fully deployed or operational. It Ensures that each node in the set of nodes can be
20

accessed or contacted. Further, the reachability parameter refers to a measure or
criterion used to determine whether a network component (such as a node) is
reachable over the network. This parameter might involve checking network
connectivity, response times, or other indicators. This might involve checking
5 network connectivity to confirm that each node can communicate with the others
as required and verifies that the login credentials provided for each node are correct
and can be used to successfully log into each node. Further, the predefined
validation rules may include a set of pre-defined criteria to validate various aspects
of the container orchestration deployment. Examples of such pre-defined criteria
10 may include, but are not limited to, rules to verify the integrity of the deployment
configuration, checking compliance with security policies and configuring resource
allocation limits. However, it may be noted that such pre-defined criteria as
mentioned above are only exemplary, and in no manner to be construed to limit the
scope of the present subject matter in any manner. Any other examples of pre-
15 defined criteria may also be used, and would lie within the scope of the present
subject matter.
[0062] At step 308, the method comprises, initiating, by a deployment unit [205],
a predetermined deployment based on the validation of the at least one of the
20 reachability parameter and the input login credentials and automate, the container
orchestration deployment based on the predetermined deployment. The present
disclosure encompasses that the deployment unit [205] waits for a signal from the
validation unit [203] indicating that the reachability of nodes and the validity of
login credentials have been confirmed according to predefined rules The
25 deployment unit [205] has two main functions:
• Initiate Predetermined Deployment: Once the validation unit [203] confirms
that the reachability parameters and input login credentials are valid, the
deployment unit [205] begins the deployment process as specified in the
deployment plan. The predetermined deployment refers to a deployment
30 process that follows a predefined and automated sequence of steps and
configurations.
21

• Automate Container Orchestration Deployment: The deployment unit [205] automates the setup and management of containerized applications, using a predetermined deployment method.
5 [0063] In one example, the predetermined deployment may be a Kubernetes
deployment to automate the container orchestration deployment. The term
automation refers to the process where the deployment unit [205] carries out the
deployment tasks without manual intervention. This involves using predetermined
deployment related data, such as configuration files, deployment scripts, and
10 environment settings.
[0064] At step 310, the method comprises, automating, by the deployment unit
[205], the container orchestration deployment based on the predetermined
deployment. In one example, the predetermined deployment is a Kubernetes
15 deployment to automate the container orchestration deployment.
[0065] Further comprising configuring by the deployment unit [205] at an Automated Cloud Installer (ACI) at least one of a secured shell internet protocols (SSH IPs) associated with the one or more master nodes, a SSH IPs associated with
20 the one or more worker nodes, a SSH IPs associated with the one or more load
balancer nodes, and a Virtual IP associated with the one or more load balancer nodes based on a user input. The present disclosure encompasses the ACI is a tool or platform that automates the deployment of cloud infrastructure and services. It sets up process by handling complex configurations automatically. The deployment unit
25 [205] configures the SSH IP addresses for the master nodes. These IP addresses are
used to securely access and manage the master nodes over the network. Similarly, the deployment unit [205] configures the SSH IP addresses for the worker nodes, and load balancer nodes. The deployment unit [205] configures a Virtual IP (VIP) for the load balancer nodes. The VIP is a single IP address that can represent a group
30 of load balancer nodes, providing a consistent endpoint for distributing traffic
across multiple nodes. The configurations for SSH IPs and the VIP are based on
22

user input, this means that the user provides the necessary information or preferences, and the deployment unit [205] uses this input to set up the IP addresses accordingly.
5 [0066] Furthermore, initiating by the deployment unit [205] the predetermined
deployment further comprises identifying, by the deployment unit [205] via the ACI, a successful login associated set of nodes based on the input login credentials, re-configuring, by the deployment unit [205], one or more preconfigured configurations associated with the at least the one or more master nodes and the one
10 or more worker nodes based on the successful login, deploying, by the deployment
unit [205], the one or more load balancer nodes based on reconfiguring the one or more preconfigured configurations. Further installing, by the deployment unit [205], a set of tool packages at least at the one or more master nodes and the one or more worker nodes based on deploying the one or more load balancer nodes. the
15 method further comprising initiating, by the deployment unit [205], a set of
commands based on installing the set of tool packages, generating, by the deployment unit [205], a set of logs based on at least the set of commands, and transmitting, by the transceiver unit [201] via a user interface, the set of logs based on at least the set of commands. The deployment unit [205] verifies that the input
20 login credentials work for each node (master, worker, load balancer) by attempting
to log in via the ACI. After successfully logging in, the deployment unit [205] reconfigures existing settings or configurations on the master and worker nodes as needed to prepare them for deployment. Using the reconfigured settings, the deployment unit [205] deploys the load balancer nodes to manage network traffic
25 and distribute workloads. Once the load balancer nodes are deployed, the
deployment unit [205] installs necessary tool packages (for example, kubectl, kubeadm, kubelet, kubernetes-cni and cri-tools) on the master and worker nodes. These tools, in an example, may include monitoring agents, security tools, or other utilities required for operation. With the tool packages installed, the deployment
30 unit [205] executes a set of predefined commands to further configure the system,
start services, or perform other tasks needed to finalize the deployment.
23

[0067] In one example, during the execution of commands, the deployment unit
[205] runs kubeadm init and kubeadm join command to ensure kubernetes cluster
is successfully deployed and ready to work. As would be understood, the kubeadm
5 init command is a Kubernetes command-line tool used to initialize a new
Kubernetes control plane. Further, kubectl is the command line tool used to interact with Kubernetes clusters. The kubectl allows users to manage and deploy applications, inspect and manage cluster resources, and view logs. The kubeadm is a tool that simplifies the process of setting up a Kubernetes cluster. The
10 kubernetescni (Container Network Interface) is a set of standards and libraries used
for configuring networking interfaces in Linux containers. The cri-tools are a set of command line tools used to interact with the Container Runtime Interface (CRI) of Kubernetes. When executed, it sets up the necessary components and configurations to create a functional Kubernetes cluster.
15
[0068] It may be noted that the above-mentioned commands are only exemplary and in no manner to be construed to limit the scope of the present subject matter in any manner. Other types of commands may also be used by the deployment unit [205] and would lie within the scope of the present subject matter.
20
[0069] Continuing further, the deployment unit [205] then generates logs that capture the output and status of these operations. These logs are the records of events and actions taken during the deployment and operation of containers. For example: container logs showing output from running applications,. The
25 orchestration logs detailing actions taken by the orchestration tool, etc. The ACI
also writes script logs of above steps to local file (on deployment host) and send real time logs to GUI. These logs will provide valuable information for troubleshooting and resolving any server-level issues that may arise. Further, the transceiver unit [201] then transmits these logs to the user through a user interface,
30 providing feedback on the deployment status and any issues that may have
occurred.
24

[0070] The data and instructions are stored, by the storage unit [207] associated with implementation of the features of the present invention.
5 [0071] Thereafter, the method terminates at step 312.
[0072] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for automating a container orchestration deployment, the instructions include executable code which, when executed by one
10 or more units of a system, causes a transceiver unit [201], of the system [200], to
receive a deployment plan comprising at least an input login credentials associated with a set of nodes. Further, the instructions include executable code which, when executed causes a validation unit [203], of the system [200], to validate at least one of a reachability parameter associated with the set of nodes and the input login
15 credentials associated with the set of nodes based on a predefined validation rules.
Further, the instructions include executable code which, when executed causes a deployment unit [205], of the system [200], to: initiate a predetermined deployment based on the validation of the at least one of the reachability parameter and the input login credentials; and automate, the container orchestration deployment based on
20 the predetermined deployment.
[0073] As is evident from the above, the present disclosure provides a technically advanced solution for automating a container orchestration deployment. The present solution provides the ability to use the COS even when there is insufficient
25 internet connectivity. Further, the present solution is time-efficient to deploy the
COS and reduces chances of error while deploying the COS. Also, the implementation of automated COS cluster creation greatly accelerates the deployment of network functions within the infrastructure. The user does not need to possess any technical expertise or knowledge in order to operate the ACI.
30
25

[0074] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
principles of the present disclosure. These and other changes in the implementations
5 of the present disclosure will be apparent to those skilled in the art, whereby it is to
be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0075] Further, in accordance with the present disclosure, it is to be acknowledged
10 that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed
15 as limiting the scope of the present disclosure. Consequently, alternative
arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
26

We Claim:
1. A method for automating a container orchestration deployment, the method
comprising:
- receiving, by a transceiver unit [201], a deployment plan comprising at least an input login credentials associated with a set of nodes;
- validating, by a validation unit [203], at least one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules;
- initiating, by a deployment unit [205], a predetermined deployment based on the validation of the at least one of the reachability parameters and the input login credentials; and
- automating, by the deployment unit [205], the container orchestration deployment based on the predetermined deployment.

2. The method as claimed in 1, wherein each of the set of nodes comprises at least one of one or more master nodes, one or more worker nodes, and one or more load balancer nodes.
3. The method as claimed in 2, further comprising: configuring by the deployment unit [205] at an Automated Cloud Installer (ACI) at least one of a secured shell internet protocols (SSH IPs) associated with the one or more master nodes, a SSH IPs associated with the one or more worker nodes, a SSH IPs associated with the one or more load balancer nodes, and a Virtual IP associated with the one or more load balancer nodes based on a user input.
4. The method as claimed in 3, wherein initiating by the deployment unit [205] the predetermined deployment further comprises:
- identifying, by the deployment unit [205] via the ACI, a successful login
associated set of nodes based on the input login credentials,

- re-configuring, by the deployment unit [205], one or more preconfigured configurations associated with the at least the one or more master nodes and the one or more worker nodes based on the successful login,
- deploying, by the deployment unit [205], the one or more load balancer nodes based on reconfiguring the one or more preconfigured configurations,
- installing, by the deployment unit [205], a set of tool packages at least at the one or more master nodes and the one or more worker nodes based on deploying the one or more load balancer nodes,
- initiating, by the deployment unit [205], a set of commands based on installing the set of tool packages,
- generating, by the deployment unit [205], a set of logs based on at least the set of commands, and
- transmitting, by the transceiver unit [201] via a user interface, the set of logs based on at least the set of commands.

5. The method as claimed in the claim 1, wherein the predetermined deployment is a Kubernetes deployment to automate the container orchestration deployment.
6. A system for automating a container orchestration deployment, the system comprising:

- a transceiver unit [201] configured to receive, a deployment plan comprising at least an input login credentials associated with a set of nodes;
- a validation unit [203] connected to at least the transceiver unit [201], the validation unit [203] configured to validate at least one of a reachability parameter associated with the set of nodes and the input login credentials associated with the set of nodes based on a predefined validation rules; and

- a deployment unit [205] connected to at least the validation unit [203],
the deployment unit [205] configured to:
o initiate a predetermined deployment based on the validation of the at least one of the reachability parameter and the input login credentials, and
o automate, the container orchestration deployment based on the predetermined deployment.
7. The system as claimed in 6, wherein each of the set of nodes comprises at least one of one or more master nodes, one or more worker nodes, and one or more load balancer nodes.
8. The system as claimed in 5, wherein the deployment unit [205] is further configured to configure, at an Automated Cloud Installer (ACI), at least one of a secured shell internet protocols (SSH IPs) associated with the one or more master nodes, a SSH IPs associated with the one or more worker nodes, a SSH IPs associated with the one or more load balancer nodes, and a Virtual IP associated with the one or more load balancer nodes based on a user input.
9. The system as claimed in 8, wherein for initiation of the predetermined deployment, the deployment unit [205] is further configured to:

- identify, via the ACI, a successful login associated set of nodes based on the input login credentials,
- re-configure, one or more preconfigured configurations associated with the at least the one or more master nodes and the one or more worker nodes based on the successful login,
- deploy, the one or more load balancer nodes based on reconfiguring the one or more preconfigured configurations,
- install, a set of tool packages at least at the one or more master nodes and the one or more worker nodes based on deploying the one or more load balancer nodes,

- initiate, a set of commands based on installing the set of tool packages,
- generate, a set of logs based on at least the set of commands, and wherein the transceiver unit [201] is further configured to transmit, via an user interface, the set of logs based on at least the set of commands.
10. The system as claimed in the claim 6, wherein the predetermined
deployment is a Kubernetes deployment to automate the container orchestration deployment.