Strong and weakness

My Weak Areas:

  1. Advanced Networking in Kubernetes:
    While I can work with basic network policies, ingress controllers, and load balancers, I am still working on mastering advanced networking concepts like service meshes (e.g., Istio).
  2. Programming Skills Beyond Automation: My Python and shell scripting are strong for automation tasks, but my experience with developing more complex applications or advanced programming concepts could be improved.
  3. Multi-Cloud Expertise: My experience is primarily focused on AWS. I am less familiar with Azure or GCP but am eager to upskill to support multi-cloud environments.

Strong Area:

  1. CI/CD Pipelines: Proficient in designing, implementing, and maintaining CI/CD pipelines using tools like Jenkins, GitHub Actions, and Argo CD. This includes stages for testing, code analysis, security scanning, and deployments.
  2. Containerization & Orchestration: Strong experience with Docker and Kubernetes, including creating Dockerfiles, Kubernetes YAML manifests, managing EKS clusters, and using tools like Trivy for container security.
  3. Infrastructure Automation: Skilled in writing Ansible playbooks for configuration management and automating deployments across environments. Also adept at Terraform for infrastructure as code.
  4. Cloud Services (AWS): Expertise in AWS, including EC2, S3, VPC, ELB, IAM, ECR, and Route 53. Can design highly available, fault-tolerant applications leveraging AWS services.
  5. Monitoring & Alerting: Experienced in setting up monitoring with Prometheus and Grafana, as well as AWS CloudWatch for alerts and log management.
  6. Problem-Solving: Strong analytical skills in troubleshooting issues like failed deployments, Kubernetes node upgrades, and resource allocation challenges.

Hobbies

Example Answer for Hobbies:

“I enjoy exploring new technologies and experimenting with tools in my personal lab environment. For instance, I recently set up a Kubernetes cluster at home to better understand advanced configurations.

On a more personal level, I enjoy playing team sports like cricket or football, as they help me unwind and improve my teamwork skills, which I find valuable even in a professional setting.”

How You are updating yourself with new technology ?

“I make it a priority to stay current with the rapidly evolving technology landscape, especially in the DevOps field. Here’s how I do it:

  1. Online Resources: I follow leading platforms like Medium, DevOps.com, and the AWS Blog to stay informed about new tools, trends, and best practices.
  2. Learning Platforms: I regularly take courses on platforms like Udemy, Coursera, and Pluralsight to deepen my understanding of new technologies.
  3. Hands-On Practice: I have a personal lab setup where I experiment with tools and concepts I encounter, such as exploring advanced Kubernetes features or trying out new CI/CD tools.
  4. Community Engagement: I participate in DevOps-focused webinars, tech meetups, and conferences, where I learn from industry experts and exchange ideas with peers.
  5. Certification and Training: I pursue certifications in areas relevant to my role, like AWS and Kubernetes, which help me stay structured in my learning.
  6. Collaboration: I engage with colleagues and teams to discuss innovative approaches and share knowledge, which broadens my perspective on how to solve problems.

One thing you hate most in devops ?

“One thing I dislike the most in DevOps is handling repetitive manual tasks that could be automated but aren’t due to time constraints or organizational priorities. While automation is a core principle of DevOps, sometimes immediate deadlines force us to handle things manually, which can feel inefficient. I always try to find time later to automate such processes and make them smoother for the future.”

What is the toughest challenge you faced in your career ?

One of the toughest challenges I faced was with the “ibis” microservice , which is critical for automating infrastructure tasks. Oneday , the ibis service unexpectedly failed after a routine configuration update. This caused automation workflows to halt, impacting multiple dependent systems. The issue was critical, as it disrupted ongoing operations and escalated to senior management.

During troubleshooting, I discovered that the Raptor service was failing due to a conflict between the updated configuration and the external database it was using. Specifically, the logs indicated an error: Database connection timeout: failed to retrieve metadata. This pointed to an issue with the database connection parameters.

Steps to Resolve:

  1. Log Analysis: I first reviewed the logs using monitoring dashboard and CLI tools. The logs showed that the ibis service was attempting to connect to a database endpoint using an outdated TLS version due to a mismatch in the security settings introduced by the update.
  2. Rollback Attempt: I attempted to roll back the configuration changes, but the rollback failed because the service had already partially applied the new settings, making the older configuration incompatible.
  3. Root Cause Identification: I traced the issue to a misconfigured TLS version in the Raptor microservice’s configuration file (raptor-config.yaml). The service was set to use TLS 1.1, while the database endpoint required TLS 1.2.
  4. Reconfiguration:
    • I updated the raptor-config.yaml file to enforce TLS 1.2 under the database.connection.security section.
    • I also adjusted the database connection pool parameters (maxPoolSize and connectionTimeout) to handle high request loads better, as the default values were insufficient for peak operations.
  5. Service Restart and Validation:
    • I restarted the Raptor service using the CLI (systemctl restart raptor).
    • I ran a series of automated health checks and manually triggered a few automation tasks to validate the fix.
  6. Database Performance Optimization: To ensure stability, I also applied a performance tuning update to the database, optimizing query execution plans and clearing connection locks.

What is devops ?

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to improve collaboration, automate processes, and enhance software delivery. It emphasizes continuous integration (CI), continuous delivery/deployment (CD), infrastructure as code (IaC), and monitoring. The goal is to deliver high-quality software quickly and efficiently.

Benefits of DevOps:

  • Faster Time to Market: Accelerates the delivery of new features and updates.
  • Improved Quality: Enhances software quality through automated testing and continuous integration.
  • Increased Efficiency: Reduces manual tasks and increases productivity through automation.
  • Better Collaboration: Fosters a culture of collaboration and shared responsibility.
  • Enhanced Reliability: Improves system reliability and uptime through continuous monitoring and automated deployment.

Introduction:

–> I completed my engineering from BPUT in 2018 and started my career at Blackknight in 2020 as fresher
–> Later In 2022, I joined HCL Tech
–> I have overall 4 years of experience in devops and cloud.
–> I Worked for various tools for build and release engineering, even automation and orchestration

–> To create infrastructure for environment like dev, QA, stage and production
–> Building CICD pipeline, so in my project we used Jenkins and GitHub as ci tool
–> writing the dockerfile for creating images.
–> writing Kubernetes YAML file for the deployment
–> Debugging the application if in case of any issues
–> Monitoring the entire Application
–> we are using the ansible for downloading and updating multiple dependencies in the host machines at the same time

Coming to the AWS cloud part
–> I have good knowledge in EC2, Storage, IAM, S3, VPC, ELB, EKS, SNS, Route53 services in AWS.

Describe your “most significant achievement” in the DevOps role. How did your contributions impact the team or organization?

Leave a Comment