Devops Cloud Engineer Resume
3.00/5 (Submit Your Rating)
PROFESSIONAL EXPERIENCE
Confidential
DevOps Cloud Engineer
Responsibilities:
- Developing and maintaining CI/CD Pipelines for Micro Service based applications using Jenkins/Microsoft Azure.
- Created branching strategies in Github for newly developed VSTS pipelines and set up automated deployments to reduce time consumed by manual deployments.
- Designing and maintaining containerized microservices and configuring/maintaining private container registry on Microsoft Azure and GCP for Hosting Images.
- Making deployments of microservices as conatiners by using containerization tools like docker and Docker compose. Docker swarm and kubernetes for orchestration and jenkins/Microsoft Azure to ensure continuous deployments in to the different environments.
- Monitoring the pipelines through the process of development, test and release of an application actively spotting the bottlenecks and fixing them thereby enabling seamless deployments.
- Building Infrastructer using terrform scripts. Written Terraform scripts for various projects to create GKE Clusters and AWS EC2 instances along with S3 storage buckets.
- Used configuration management tools like Ansible and chef to manage the Nodes and servers created in GCP and AWS.
- Wrote ANSIBLE Playbooks and used SSH as the Wrapper to Manage Configurations of GCP Nodes and Test Playbooks n GCP instances using Python.
- Creating Different environments for multiple projects (i.e. CICD, Dev, Test, Stage and Production) in Google Cloud(GCP) and Azure Platforms.
- Automating the day to day manual process of creating Insatnces and stages for pipelines by using groovy, shell and terraform scripts.
- Implementing Cloud Armor and ACL rules to protect the environments and VPC from being corrupted by the outside network.
- Monitoring Jenkins jobs/Build & Release pipelines and helping the developers to find the root cause for the failures and troubleshooting the issues.
- Integrating Monitoring tools like Splunk and AppDynamics in to the CICD pipeline based on client requirements.
- Collaborating with multiple teams like NIS and CloudOps to setup Veracode profiles, ASA scans, Firewall rules and load balancer IP’s for the applications.
- Creating IAM policies in GCP ans AWS for providing access and restrict the access at different levels to different individuals associated to the Project.
- Estimate the cost of the tools to be integrated in to the pipeline and help the client to choose between the similar services/tools available in the market.
- Creating storage buckets and creating log sink to export container logs from the stackdriver to storage buckets in GCP.
- Migrating Docker images from one Artifacts to the Another whenever required to avoid the data being corrupted.
- Creating Kubernetes files for making the side car deployments into the cluster along with the Microservices.
Confidential
DevOps Engineer
Technologies Used: VSTS, GitHub, Rancher, Kubernetes, Docker, Azure, GCP, AppDynamics and Splunk.
Responsibilities:
- Responsible for creating build and release pipelines for the Microservices to make Deployments into all the environments by using VSTS.
- Established Service Connections between VSTS and other tools like Github, kubernetes.
- Deployed VSTS agents in to the rancher using yaml scripts and used them to make deployments through release pipelines.
Confidential
DevOps Engineer
Technologies Used: Jenkins, GitHub, Portainer, Docker, Docker swarm, GCP, AppDynamics and splunk.
Responsibilities:
- Responsible for creating Node pools, VM instances, Instance groups, Kubernetes Clusters in GCP.
- Responsible for Creating VPC, subnets, HTTP and HTTP load balancers and configuring nginx reverse proxy.
- Worked on creating certificates and DNS for the Microservices and created secrets using Portainer service.
- Created a CICD environment in GCE (Google Compute Engine) and deployed jenkins as a docker conatiner using groovy scripts.
- Created firewall rules to allow traffics from the kubernetes cluster to the services within the pwcinternal network.