DevOps Engineer
Samara, RussiaДжуниор • Миддл
Удаленная работа
Опыт работы от 1 года до 3х лет
Опыт работы от 1 года до 3х лет
Короткая ссылка: gkjb.ru/gyy4
О себе
На данный момент DevOps Engineer.
Мои компетенции и опыт
Implementation of CI/CD with Kubernetes and Terraform for a Microservices Application
— What was the challenge?
The company used a monolithic web application that was manually deployed to a single server.
This led to downtime during releases, long feature delivery times, and difficulties with scaling.
The business planned to migrate to a microservices architecture in Kubernetes, but there was no existing DevOps infrastructure for automation.
— What did I do?
— Wrote Terraform manifests from scratch to create a VPC, EKS cluster, S3 bucket, and RDS database.
— Configured Helm charts for deploying microservices to Kubernetes.
— Implemented a CI/CD pipeline using GitHub Actions.
— Set up Secret Management with HashiCorp Vault and integrated it with Kubernetes Secrets.
— Deployed Prometheus + Grafana for monitoring and Loki for centralized logging.
— Optimized the pipeline: reduced build time by 40% through Docker layer caching.
— Technology stack:
AWS, Docker, Kubernetes, EKS, Terraform, Helm, GitHub Actions, ArgoCD, Prometheus, Grafana, Loki,
Kubernetes Secrets, HashiCorp Vault, AWS IAM, Docker Compose
— What was the result?
Reduced release time from several hours to 15 minutes.
Decreased deployment errors by 70% thanks to automation.
Enabled application scalability to handle peak loads.
Secrets and configurations are now securely stored, successfully passing internal audit checks.
Improved system stability: average downtime during releases is now 0 нужен доступ к резюме entation of CI/CD with Kubernetes and Terraform for a Microservices Application — What was the challenge? The company used a monolithic web application that was manually deployed to a single server. This led to downtime during releases, long feature delivery times, and difficulties with scaling. The business planned to migrate to a microservices architecture in Kubernetes, but there was no existing DevOps infrastructure for automation. — What did I do? — Wrote Terraform manifests from scratch to create a VPC, EKS cluster, S3 bucket, and RDS database. — Configured Helm charts for deploying microservices to Kubernetes. — Implemented a CI/CD pipeline using GitHub Actions. — Set up Secret Management with HashiCorp Vault and integrated it with Kubernetes Secrets. — Deployed Prometheus + Grafana for monitoring and Loki for centralized logging. — Optimized the pipeline: reduced build time by 40% through Docker layer caching. — Technology stack: AWS, Docker, Kubernetes, EKS, Terraform, Helm, GitHub Actions, ArgoCD, Prometheus, Grafana, Loki, Kubernetes Secrets, HashiCorp Vault, AWS IAM, Docker Compose — What was the result? Reduced release time from several hours to 15 minutes. Decreased deployment errors by 70% thanks to automation. Enabled application scalability to handle peak loads. Secrets and configurations are now securely stored, successfully passing internal audit checks. Improved system stability: average downtime during releases is now 0 minutes.
Навыки: GitHub Actions · Ansible · NoSQL · Kubernetes · VPN · Python · Docker · Loki · PostgreSQL · Virtualization · Linux · Nginx · Kubernetes Secrets · Системное администрирование Linux · Terraform · MongoDB · HashiCorp Vault · AWS · Prometheus · Git · Bash · Grafana · Docker-compose · Helm
