Add some tasks examples and update format a bit
ci/woodpecker/push/spellcheck Pipeline is pending Details
ci/woodpecker/push/build Pipeline was successful Details

This commit is contained in:
Nikolai Rodionov 2024-04-23 14:47:30 +02:00
parent ba7f7e5310
commit db9e85216c
Signed by: allanger
GPG Key ID: 0AA46A90E25592AD
2 changed files with 20 additions and 6 deletions

View File

@ -37,6 +37,9 @@ mysql
percona
redis
ceph
CRDs
RabbitMQ
postgres
- index.md
Rodionov
db-operator

View File

@ -1,4 +1,8 @@
---
pdf_options:
format: a4
margin: 20mm 10mm
printBackground: true
stylesheet:
- https://cdnjs.cloudflare.com/ajax/libs/github-markdown-css/5.5.1/github-markdown.css
body_class: markdown-body
@ -20,17 +24,24 @@ css: |-
### About me
I'm a DevOps engineer with 5++ years of hands-on experience with a decent amount of tools. My main focus is Kubernetes and CI/CD.
I've got some beliefs that should be capable of describing myself
I'm a DevOps engineer with 5++ years of hands-on experience with a decent amount of tools. My main focus is Kubernetes and CI/CD, but it absolutely doesn't mean that I would like to avoid tasks on other areas.
As an engineer, I've got some beliefs and I hope that they should be capable of describing me, because that what I'm trying to bring with me:
- One should tend not to repeat oneself
- One should never edit what's constantly generated
- One should aim for lesser amount of work with a bigger outcome
- Unless something is in CI, it doesn't exist
- Human factor must be avoided when possible
- Any routine must be automated, because otherwise it's error-prone
A couple of bigger tasks I've been working on:
- A migration of several MySQL Percona clusters to Kubernetes using the Percona Operator
- An implementation of a downtime-free blue-green deployment for RabbitMQ
- A dynamic "preview" environments deployment using ArgoCD
- A data streaming automation from ~800 Postgres databases with structural changes via Kafka deployed to Kubernetes
- An introduction of versioned Gitlab-CI templates for replacing per-repo pipelines
Also, I'm a maintainer of a kubernetes operator that should help users manage databases via CRDs: <https://github.com/db-operator/db-operator>
### Experience
| Company | Position | Dates |
@ -54,4 +65,4 @@ I've got some beliefs that should be capable of describing myself
- **Secrets/Encryption**: Sops - Age - Helm Secrets
- **Databases**: PostgreSQL - MySQL - Percona MySQL - Redis
- **Storages**: Minio - Ceph - Longhorn
- **Others**: Kafka - RabbitMQ - Selenium