Posts

Logging ??

Image
 Today we will learn about the following things: What is logging ?? Why do we need logging ?? How can logging help us ?? Why suddenly from the last 5-10 years logging has been evolving ?? Logging tools ?? First thing first, let's start with logging. Logging is human-readable information that is primarily text in nature. Logging is triggered or generated when some kind of event occurs, such event is known as a log event.  Each logging message contains the timestamp, which signifies the time at which the event occurred. Now let, us understand why we need logging.  Importance of logging ?? In today's world software all around the world captures the whole market. By definition, Software is a program that is made up of millions of lines of code.  The programmer while writing the code adds the logs at all places to know the code behaviors as well as unexpected ones.  The logs can be of types such as ERROR, WARN, INFO, FATAL, DEBUG, TRACE, etc.     NOTE : Logs are also added to know w
Post a Comment
Read more

Application Resource in Argo CD

Application Resource   I hope you remember this question in the previous blog: " But how does the Argo CD operator know about the source and destination? ". These all are declared in a custom resource definition(CRD) called Application . It has a source field, a destination field, and many more fields. In order to differentiate b/w source and destination, simply ask this question: For Source : From where to fetch/pull the manifest or configuration files?? For Destination : And where to deploy these manifests or configuration files?? So, the Argo CD operator i.e. application controller uses application resources to achieve the desired state in the cluster with the help of the reconciliation concept. Let's understand the terminologies used in the Application. Argo CD Concepts and Terminologies ?? Terminologies to be used while writing an application resource: The application has 3 main components: Destination : This refers to clusters to which manifest to be deployed or t
Post a Comment
Read more

Argo CD 101

Image
Why Argo CD ?? Because it fulfills all the points of the GitOps principle . As it extends the benefits of declarative specifications, acting as a GitOps Operator, follows a pull-based approach,  and considers Git as a source of truth for configuration management. It follows a pattern of reconciliation i.e. continuously performing a control loop every 3 minutes to achieve the desired state by fetching the desired configuration from Git. Let’s understand it in more detail, how can we achieve or implement GitOps using Argo CD ?? We all know that every company and every developer uses Git as a source code management software to store code. Developers can commit their infrastructure configurations, such as Kubernetes resource manifest, in Git to create the environment needed for application deployment. Once a developer implements a feature( with new applications and Kubernetes configurations) and merges the main branch. With the help of the GitOps agent or GitOps operator, Argo CD will imme
Post a Comment
Read more

What is GitOps in easy way ??

Image
Here we will discuss: "What is GitOps", and "What are its 4 important principles". And lastly, "Why GitOps operator follow a pull-based model ?". What is GitOps ?? GitOps is made up of two words: Git and Ops . Git is where you keep your desired manifest(or configurations) that you want to deploy in your cluster(or environment). And Ops refers to Operation. Operation refers to the environment where the things are operated to ensure that the actual state or live state of that environment must be the same as the desired state in the git. To achieve that from the actual state to the desired state an operation is performed inside the environment.  Such an environment could be a Kubernetes cluster. So, anything that you want to deploy in the Kubernetes simply put it in the git. From git, the GitOps operator(i.e. Argo CD) will deploy to the Kubernetes cluster. To understand the GitOps better we need to understand 4 principles of it: 4 Principles of GitOps: 1.
Post a Comment
Read more