Il'Ya Tishchenko Email & Phone Number

Limassol, Cyprus

* Created a single repository for Ansible using its galaxy roles, each role is performed with testing in molecule. Using Gitlab CI for CI/CD , configured the entire pipeline flow.* Update the ELK stack by moving from old servers to new ones, completely updated the snapshot policies with entries in S3, updated ILM policies for all indexes. Automated the process of working with ELK via ansible* Automated the installation and configuration of redis sentinel / redis cluster and some other services.* Import and update state for Cloudflare using terraform* Performed terraform/terragrunt tasks when working with AWS* I took on most of the monitoring tasks, tried to use the experience gained from my previous role. I introduced long-term work. Except Prometheus, I hooked up Victoria Metrics to work* Put into operation an opentelemetry system using grafana Tempo* Work on duty tasks - analysis and assistance in solving problems with the installation and operation of applications in openshift/kubernetes, solving errors in CI/CD jobs* SRE / duty - analysis and elimination of problems in зroduction

Cyprus

Ansible:Developed and wrote Ansible roles and playbooks to automate the deployment and management of various services such as Redis, Elasticsearch, Prometheus, and its exporters and others.Managed inventories in Ansible to streamline and optimize infrastructure configurations.CI/CD:Designed and maintained CI/CD pipelines using GitLab, primarily for deploying Helm applications in Kubernetes (OKD) and managing infrastructure with Ansible.Use secrets from HC Vault for any sensitive information.Helm:Worked extensively with Helm for deploying, and managing Kubernetes applications.Created and customized Helm charts to standardize the deployment of microservices.Terraform:Described and managed infrastructure using Terraform, with a focus on Cloudflare and AWS environments.Monitoring, Prometheus:Configured monitoring systems using Prometheus.Created and optimized alerts for timely incident response.Improved existing alerts to enhance accuracy and reduce false positives.Managed alerts related to both infrastructure metrics and business-critical.SRE:Participated in on-call rotations, providing 24/7 support and incident response.Ensured high availability and reliability of services, rapidly addressing emergencies.

Moscow

Sberbank is the largest bank in Russia.Working in ci/cd team, have been developing pipeline as a service for more then 20 development teams.Pipeline based on Jenkins with using groovy. Openshift/Kubernetes: Pipeline using in installation processes for delivery applications in openshift clusters.HELM: Helping development teams with migration on kubernetes and using helm templatingAnsible: We using Ansible for most steps in. Writing roles, playbooks, writing Ansible modules in PythonDocker: preparing dockerfiles for the team services and helping other development teams with their, using own registry, docker-compose scriptsCheckov: add custom policies and modify code for our requirements, checks have been integrating in pipeline.Zabbix: Made monitoring for several CRM Siebel stands.ELK stack: Installation for the needs of the team, using pipelines to add data from filebeats and own python libraries.

Moscow, Russia

Automation of scheduled tasks using Bash, Powershell. Working with MySQL databases - tuning, replication\backups\monitoring. Supporting Zabbix monitoring systems. Created and systematized the technical documentation of the operation department. Commissioning of Rundeck, RocketChat system for better expereince between dev and ops teams.Technologies used: RHEL 6/7, Apache, Nginx, PHP-FPM, Mysql, Zabbix.

Moscow, Russia

• Linux (CentOS, Debian) - setting up iptables rules, squid configurationsfor caching, transferring web servers from apache to nginx simplifiedworking with services, virtual RAID mdadm was mainly used on servers,transferring from the 5th raid to the 6th, writing bash scripts - automatingvarious tasks• Windows - 2008 R2, 2012 K2, AD: Configuring users and machinepolicies, updating the server 2008 R2 to 2012 with the preservation of theentire AD configuration.• SVN, Redmine, ODOO, Mantis, OTRS - SVN was used as the mainVCS, introduced a test Redmine for preliminary testing of updates and newplugins, Mantis was used as the main system for the company's customers,OTRS was introduced for internal tickets, ODOO was selected as atransitional option with Mantis• Introduced GIT with launch sevrer with gitlab• Hyper-V, Vmware ESXi, Proxmox: vmware virtual machines were usedby developers as test benches, Proxmox was used for a web server thatwas migrated from a physical one.• Asterisk, SIP, IAX - configuration and rules setup, voice menu creation• Network monitoring - configured system monitoring with SMS notificationusing ZABBIX, SNR-ERD and sensors were used to monitor the state ofequipment in the server room, temperature.• Providing remote access to employees via VPN (Windows) andconfiguring access to machines via TigerVNC• Configuring backups for databases and file servers• Mysql, MSSQL - administration, configuration optimization, backupconfiguration• Working with network equipment (HP, Netgear, D-Link, SNR, Cisco,Zyxel) - SNR switches were chosen as the main equipment for working inthe enterprise because of the price and capabilities.• Documentation, inventory of the information structure: simple softwarefor work such as KeePass, dokuwiki, Frendly Pinger• Technical support for users working with software and office equipment• Translation of technical documentation in English, correspondence inEnglish