Apache NiFi is an easy-to-use, powerful, and reliable system to process and distribute data. As data flows between different systems it’s a good practice to ensure the integrity of the data being processed. Securing a NiFi cluster is essential for various reasons, primarily to protect sensitive data, ensure system integrity, and prevent unauthorized access. Apache NiFi provides a TLS toolkit using which we can self-sign Certificate Authority (CA) and easily issue and sign certificates in the format expected by NiFi. Continue reading “Securing Nifi Cluster with TLS Toolkit”
Tag: technical blog
How to get Java heap dump from Kubernetes container into a local machine?
To get a Java heap dump from a Kubernetes container to your local system, first create a dump file inside the pod using a JDK tool like jmap or jcmd. Once the dump file is created, you can copy the file to your local system using the kubectl cp command.
Overview
Java is renowned for its robust garbage collector algorithm, but this doesn’t completely eliminate the risk of memory leaks in JVM applications. To identify potential leaks in your application, the first step is to obtain and analyze a heap dump.
In this short tutorial, we’ll learn how to obtain a Java heap dump from an application running as a Kubernetes pod.
First, we’ll explain the definition of a heap dump, then create a small test application that will be deployed as a pod in Kubernetes. Finally, we’ll walk through the process of obtaining a heap dump from that application.
Continue reading “How to get Java heap dump from Kubernetes container into a local machine?”
Jenkins Job Creation using Multibranch Job DSL
To set up a Jenkins Multibranch Pipeline job via the Job DSL plugin, you must create a Groovy script within a “seed” job that programmatically outlines the multibranch configuration. This Job DSL script will then create the actual Multibranch Pipeline job.
Introduction
In this blog, we will explore the world of Jenkins job DSL and learn how to leverage its capabilities to streamline and automate job configuration management. We will walk through the process of setting up the Job DSL environment, writing Job DSL scripts to define different types of jobs, managing job configurations as code, and integrating Job DSL with your CI/CD pipelines. Continue reading “Jenkins Job Creation using Multibranch Job DSL”
Terraform Version Upgrade
Starting the blog with the question – What is Terraform?
It can be called a magic wand that creates Infrastructure on the basis of the code that you write.
In Hashicorp’s words, “Terraform is an open-source Infrastructure as A Code software tool that enables you to safely and predictably create, change, and improve infrastructure.“
Continue reading “Terraform Version Upgrade”What is a Bare Git Repository?
A Git bare repository is a specialized version of a Git repository that serves a different purpose than a regular Git repository. Many platforms, such as GitHub, rely on bare repositories stored on their servers. When you clone a repository from GitHub, you’re actually accessing one of these bare repositories. They’re designed for server-side use, helping to securely and efficiently manage and distribute code, without the ability to directly modify files like a normal repository. Here’s a simple explanation:
- Lack of a working directory: Unlike standard Git repositories, bare repositories don’t have a working directory. This means you can’t view or edit files directly. You also won’t be able to run Git commands that typically require a working directory.
- Only contains Git data: A bare repository only contains the .git folder data you’d find in a normal repository. This includes version history, configuration, branches, etc., but it doesn’t include the actual project files that you can edit.
- Used for Sharing: Bare repositories are typically found on servers where multiple developers share code. Instead of working directly in the bare repository, developers clone it to their local computers, make changes, and then push those changes back to the bare repository. Services like GitHub use a similar process.
- Prevents direct editing: By not having a working directory, there’s no risk of users directly editing files on the server. This helps avoid conflicts and maintain version control.
- Simplifies management: If you’re managing a server-side repository and only need to monitor history and branches, a bare repository is a more efficient and secure option.
By understanding these details, you can appreciate the role of bare repositories in a collaborative coding environment.