Not just a CV. This site is a live CI/CD cloud project.
I built this portfolio to demonstrate real delivery engineering: GitLab source control, Jenkins pipelines, Docker images, AWS ECR, k3s deployment, Terraform-driven infrastructure and production-style observability thinking.
9 yrsDevOps / SRE experience
AWSEC2 · ECR · IAM · SSM
IaCTerraform plan/apply workflow
k3sKubernetes-style deployment
$ git push origin main
GitLab webhook → Jenkins
✓ docker build frontend/backend
✓ push images to AWS ECR
✓ kubectl rollout to k3s
Main purpose of this portfolio
Proof of hands-on DevOps delivery
Recruiters and interviewers can see the live website, then immediately understand the engineering behind it: source code, pipeline, containers, AWS registry, infrastructure automation and runtime deployment.
Core capabilities
Cloud, CI/CD, IaC and reliability
Focused on building repeatable environments, reducing manual effort, improving release confidence and keeping production systems observable.
☁️
Cloud Infrastructure
AWS-first platform work across EC2, VPC, IAM, S3, ECR, CloudWatch, SSM and production access controls.
🔁
CI/CD Automation
Jenkins pipelines that build, tag, scan, push and deploy without manual release steps.
🏗️
Infrastructure as Code
Terraform workflows with plan/apply/destroy stages, parameterised inputs and repeatable provisioning.
🐳
Containers
Frontend and backend packaged as Docker images and published to AWS ECR with immutable build tags.
☸️
k3s / Kubernetes
Namespace, deployments, services, ingress, HPA and rollout status checks for application delivery.
📈
SRE Mindset
Health checks, fast rollback thinking, observability, safe automation and operational runbooks.
How this website works?
From code change to live portfolio
This page explains the actual engineering flow behind the site. It is intentionally visible because the project is designed to prove CI/CD, cloud and IaC capability.
1
Code lives in GitLab
Frontend, backend, Dockerfiles, Jenkinsfiles, Kubernetes manifests and deployment scripts are version controlled together.
2
Jenkins pipeline builds images
On each release, Jenkins builds separate frontend and backend Docker images and tags them using the build number plus latest.
3
AWS ECR stores deployable artifacts
The pipeline authenticates to AWS ECR and pushes `portfolio-frontend` and `portfolio-backend` images to the registry.
4
k3s runs the application
Jenkins applies Kubernetes resources, restarts deployments, waits for rollout status and verifies pods and services.
5
Terraform supports repeatable infrastructure
A separate Jenkins Terraform pipeline can run plan, apply or destroy using controlled parameters such as key name and allowed SSH CIDR.
Architecture
Cloud and runtime architecture
The UI now matches the current project structure: Jenkins + AWS ECR + k3s deployment, with Terraform used for infrastructure provisioning workflows.
CI/CD
Jenkins pipeline flow
The current Jenkinsfile uses AWS region `eu-north-1`, builds frontend/backend images, pushes them to ECR, then deploys to k3s using kubectl.
9 years of DevOps engineering across government, enterprise and product environments.
2022 — Present
Senior DevOps Engineer · Mphasis / Scottish Government
Supported production-grade AWS environments, deployments, IAM/KMS/Secrets Manager and observability improvements.
Delivered Jenkins automation, environment operations, release support and cost optimisation.
Worked with Prometheus, Grafana, CloudWatch and runbooks to reduce manual support effort.
2021 — 2022
Senior DevOps Engineer · Mphasis HP
Maintained CI/CD pipelines, Docker/Kubernetes deployment workflows and automation scripts.
Worked on multi-cloud DevOps practices using AWS, Azure, Terraform, Ansible and Jenkins.
2016 — 2021
DevOps / Project Engineer · ThinkPalm / Wipro
Built CI/CD foundations using Jenkins, Docker, Kubernetes, Helm and release automation.
Supported application delivery, monitoring and production rollout activities.
Contact
Let’s connect
The message form has been removed as requested. This section now keeps direct contact links only.
Emailsarath.k@mphasis.com
Phone+44 7767 954 270
LocationUnited Kingdom
Portfoliosarathportfolio.cloud
LinkedInlinkedin.com/in/sarath-kumar-k
GitHubgithub.com/sarathk-devops
Photo: I added `profile-placeholder.svg` and configured the homepage to use `profile.jpg` first. Add your real photo as `frontend/public/profile.jpg` and it will automatically appear on the main page.
