---
title: "Adedoyin Ogunsola (@adegram) | Hashnode"
description: "AWS Cloud Engineer | DevOps | 2x AWS Certified | Terraform | Kubernetes. Read the latest articles by Adedoyin Ogunsola on Hashnode."
url: "https://hashnode.com/@adegram"
---

@adegram

# Adedoyin Ogunsola

@adegram · Joined March 2026

AWS Cloud Engineer | DevOps | 2x AWS Certified | Terraform | Kubernetes

### [Built a Secure CI/CD Pipeline with Jenkins: Linting, SonarQube, Trivy, and Docker Registry Push](https://adehorizon.hashnode.dev/built-a-secure-ci-cd-pipeline-with-jenkins-linting-sonarqube-trivy-and-docker-registry-push?utm_source=hashnode&utm_medium=feed)

The 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 follows this 𝗼𝗿𝗱𝗲𝗿 Lint (fail fast on cheap issues) Unit tests with coverage SonarQube scan and Quality Gate check Build the image Trivy scan of the image (and IaC config sc

2 min read · [adehorizon.hashnode.dev](https://adehorizon.hashnode.dev/built-a-secure-ci-cd-pipeline-with-jenkins-linting-sonarqube-trivy-and-docker-registry-push?utm_source=hashnode&utm_medium=feed)

[6d ago](https://hashnode.com/posts/built-a-secure-ci-cd-pipeline-with-jenkins-linting-sonarqube-trivy-and-docker-registry-push/6af5c3046772767f01d7815f)

### [Installing and Configuring Jenkins on Linux](https://adehorizon.hashnode.dev/installing-and-configuring-jenkins-on-linux?utm_source=hashnode&utm_medium=feed)

Jenkins is an open-source automation server used to automate repetitive tasks across software development and IT operations. It's used mostly used in CI and CD, schedule and execute jobs, run scripts

5 min read · [adehorizon.hashnode.dev](https://adehorizon.hashnode.dev/installing-and-configuring-jenkins-on-linux?utm_source=hashnode&utm_medium=feed)

[Sep 19](https://hashnode.com/posts/installing-and-configuring-jenkins-on-linux/6aaf0ef9f51e0cd201a29305)

### [𝗚𝗶𝘁𝗢𝗽𝘀: Argo CD + Kubernetes Cluster](https://adehorizon.hashnode.dev/argo-cd-kubernetes-cluster?utm_source=hashnode&utm_medium=feed)

It was interesting to see Argo CD implement a GitOps workflow, with the manifests stored in my Git repository. Argo CD continuously performed drift detection, comparing the live state of the Kuberne

2 min read · [adehorizon.hashnode.dev](https://adehorizon.hashnode.dev/argo-cd-kubernetes-cluster?utm_source=hashnode&utm_medium=feed)

[Sep 10](https://hashnode.com/posts/argo-cd-kubernetes-cluster/6aa1fd8eae6a70f7758023b5)

### [CrashLoopBackOff Prod-Anatomy and 10-category Kubernetes Error map](https://adehorizon.hashnode.dev/crashloopbackoff-prod-anatomy-and-10-category-kubernetes-error-map?utm_source=hashnode&utm_medium=feed)

Events are one of my first troubleshooting stops when a Pod isn't behaving as expected. I can inspect them with: kubectl describe pod <pod-name> Or kubectl get events -n --sort-by=.lastTimestamp E

4 min read · [adehorizon.hashnode.dev](https://adehorizon.hashnode.dev/crashloopbackoff-prod-anatomy-and-10-category-kubernetes-error-map?utm_source=hashnode&utm_medium=feed)

[Sep 3](https://hashnode.com/posts/crashloopbackoff-prod-anatomy-and-10-category-kubernetes-error-map/6a98be4c1ee0494720139694)

### [Solving ImagePullBackOff, CrashLoopBackOff and OOMKilled Pod-Status in K8s](https://adehorizon.hashnode.dev/solving-imagepullbackoff-crashloopbackoff-and-oomkilled-pod-status-in-k8s?utm_source=hashnode&utm_medium=feed)

The real Kubernetes troubleshooting skill isn't memorizing error names, it's knowing which layer to check next based on the symptom in front of you. kubectl describe pod <pod-name> + Events is one of

5 min read · [adehorizon.hashnode.dev](https://adehorizon.hashnode.dev/solving-imagepullbackoff-crashloopbackoff-and-oomkilled-pod-status-in-k8s?utm_source=hashnode&utm_medium=feed)

[Sep 2](https://hashnode.com/posts/solving-imagepullbackoff-crashloopbackoff-and-oomkilled-pod-status-in-k8s/6a98adef9a580ce10044adc1)
