Skip to content
View morgenvor's full-sized avatar
  • Ryazan, Russia (UTC+3)
  • 12:42 (UTC +03:00)

Block or report morgenvor

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
morgenvor/README.md

Dmitriy Kurganov

Junior DevOps Engineer — CI/CD, containers, Kubernetes, observability, infrastructure as code.

I build delivery pipelines end to end: from a git push to a verified rollout on a managed cluster, with immutable artifacts and checks that fail the build instead of the service. I also build monitoring that proves it works: SLOs, alerts whose delivery is verified, and incident drills that leave evidence. Based in Ryazan, Russia (UTC+3). Open to office, remote, and relocation.

Jenkins Docker Kubernetes Helm Terraform Ansible Prometheus Grafana Loki Linux Bash Python

Featured projects

Operating a Kubernetes service on evidence. SLOs are measured from the client's side — 99 % availability and 95 % of requests under 300 ms over a three-day window — and the alerts on top of them are multi-window burn-rate rules rather than raw thresholds. A severity-based Alertmanager route sends page mail that links the runbook, the dashboard and the log window of the incident, while everything else goes to a journal sink that records delivery. Four fault-injection drills (connection resets, added latency, a broken readiness probe, an OOM kill) write a machine-readable timeline, and an alert that fires but never arrives fails the drill.

Offline gates — promtool rule tests, kubeconform rendering, e-mail template and secret scans — run in CI, and what is proven and what is not is recorded with dates.

A Java 17 / Spring Boot service delivered by a webhook-triggered Jenkins pipeline: Gradle build and tests, Docker image pushed to Yandex Container Registry, Helmfile deployment to Managed Kubernetes, rollout checks, and an HTTP smoke test.

What it proves: releases are pinned by registry digest instead of a mutable tag, Jenkins works through a service account with namespace-scoped RBAC only, and every deploy is gated by rollout and smoke checks. The cloud environment is decommissioned, so the repository ships a Docker Compose stack that reproduces the same application and database locally.

Open source

Currently learning

  • Terraform and Ansible: reproducible infrastructure and repeatable host configuration.

Contact

  • Email: lokrost015@gmail.com
  • GitHub: @morgenvor
  • Looking for Junior DevOps / SRE, Linux system administration, or technical support (L2/L3) roles — office, remote, or relocation.

Pinned Loading

  1. k8s-observability-lab k8s-observability-lab Public

    Эксплуатация на практике: SLI/SLO и burn-rate алерты, качество алертов, доставка уведомлений, логи Loki, инцидент-дриллы на k3s

    Shell

  2. ansible-yandex-cloud-inventory ansible-yandex-cloud-inventory Public

    Ansible dynamic inventory plugin for Yandex Cloud — fork with fixes

    Shell

  3. YandexCloud-CI-CD YandexCloud-CI-CD Public

    Jenkins → Docker → Yandex Container Registry → Managed Kubernetes (Helmfile), digest-pinned releases

    Java