Looks Like This Service Is On Hold
I will set up your ci cd pipeline with github actions or gitlab ci for automated deploy
Sri Lanka
2 orders completed
DevOps Engineer Kubernetes CI CD GitHub Actions GitLab CI Azure Cloud
About this Gig
Still pushing code manually? Broken deployments costing your team hours? I will set up a production-ready CI/CD pipeline that automates your entire build, test, and depxactly what you need.loy process using GitHub Actions or GitLab CI.
I am a DevOps Engineer currently managing CI/CD pipelines and Kubernetes clusters (AKS and OKE) across Azure and Oracle Cloud for production enterprise systems. I know what reliable automation looks like because I run it every day.
What I deliver:
- Automated pipeline triggered on every push or PR
- - Docker image build and container registry push (Docker Hub, GHCR, ACR, or ECR)
- - Deploy to your server, Kubernetes cluster, or cloud environment
- - Environment-based workflows: dev, staging, production
- - Secrets and environment variable management (no hardcoded credentials)
- - Pipeline failure alerts and notifications
- - Full README documentation so your team can maintain it
Why choose me:
- Real production experience with AKS (Azure) and OKE (Oracle Cloud)
- - Hands-on with Argo CD for GitOps deployments
- - Experience with Node.js, Angular, Python, PHP, and containerized apps
- - Clear communication throughout the project
- - Complete handover documentation inc
Tools:
Docker
•
GitLab
•
Jenkins
•
GitHub
Frameworks:
Terraform
•
Ansible
Cloud Provider:
Amazon Web Services
•
Microsoft Azure
•
Oracle Cloud
Programming language:
Bash
•
Python
•
PowerShell
Expertise:
Installation
•
Debugging
•
Configuration
FAQ
Which tech stacks do you support?
I support GitHub Actions and GitLab CI with any language or framework. Common stacks include Node.js, Angular, React, Python, PHP, and containerized apps using Docker and Kubernetes (AKS, OKE, EKS, GKE).
Do I need to give you access to my servers or cloud account?
Yes, read-only or limited access is needed to deploy and test the pipeline. I use environment secrets for credentials and never store or share any access outside the project scope.
Will the pipeline work with my existing repo?
Yes. I work directly in your existing repository. I add pipeline configuration files without changing your application code. Message me first with your repo details so I can confirm the approach.
What if the pipeline does not work after delivery?
I include revisions in every package. If the pipeline has issues after delivery I will fix them within the revision scope. I test everything before delivery so this rarely happens.
