
Senior Cloud Reliability Engineer
LSEGDevOps Engineer II
NiumSystem Engineer
Tata Consultancy ServicesSoftware Engineer Intern
DishTVSoftware Developer
DishTV.png)
Jenkins

Terraform

Ansible
.png)
Docker

ECS

BitBucket

Visual Studio

Kubernetes
So I am working as a DevOps engineer. Having 4.80 years of experience, I love to solve problems. I have experience in programming languages, including Python and Bash scripting. Coming to the cloud platform, I have extensively worked on AWS cloud. In that, I have worked with DevOps tools as well. So, in that, I work on the infrastructure part, I have worked on Terraform. And, for monitoring purposes, I worked on ELK, Datadog, Grafana, and CloudWatch. For setting up alarms, I worked on CloudWatch alerts and Datadogs. Moving forward, I worked on both types of applications, monolithic and microservice-based applications. In that, I worked on microservices. I worked on Elastic Container Services as well as Elastic Kubernetes Service. In monolithic, I set up servers through automation using user data. For deployment, we use Jenkins pipelines, which is all auto deployment, configured to webhooks. I also worked on a shared library written in Jenkins. Additionally, I do some automation by converting manual tasks to automated ones. I use Python, Bash, Ansible, and Groovy scripting to write scripts, including Genkit. Yeah. That's all pretty much from my side. Thank you.
given the below poison would explain what the issue might be so basically this is the code it is written basically have which is dividing X dividing by Y so it will give the divide so let's say if it is divided by the zero it will give the infinity it will get the exception called zero division error so that is handling so it will print the message called division by zero and other than that if it anything comes it will go to the question and print out don't access and finally it will go sprint in the final block for cleanup so the issue I can see is only in this code is that XY should be always into integer when we are taking it yeah
So when we are defining SDR, we need to define it basically. We can't use some, we have to use the SDR when we're defining it. That's why it's giving a null pointer exception.
Under.append name. So based on basically adding the name and quantity at the same time to the list. It will come into a key pair, and it will be returned as a list. And when we are using a mutable list, we need to use add to a new list every time. Then we need
Let me sign in a label, it should be Nginx only. In a label in metadata label, app should be Nginx. So because when we are matching with Nginx, it should match the metadata label app NGINX only. In the template, metadata label app colon, it should be NGINX not only, but NGINX one.
How do you ensure that system is secure against cybersecurity threats? So how we can make sure the Intel Success is secure? All the, basically, database and DC instances should be in a private subnet. And in every load balancer we're using, it's going to have a WAF attached, and all the traffic we're whitelisting should be from a very specific IP, let's say 32 or specific to the service we need to attach. So let's say we use 32 or specific to the service we need to attach, and we always try to use endpoint services to route traffic from one service to another. And for security purposes, we have to restrict our IAM role access as well. And apart from that, no one can access any resource outside our network, so it should be a VPN to access any resource. And all RDS instances should be only in a restricted subnet. And always we should have a few basic programs to run automation as like, why does the idea block like 0 if it's enabled in outbound? We can filter out that, and we need to run GuardDuty alerts like that. Yeah. And also we can set up some alerts based on multiple users trying, they failed again, then we definitely need to take action.
Kubernetes helps in basically locating and scaling an application on AWS. It's basically when we're using the Horizontal Pod Autoscaler, it helps us to scale the ports in AWS, and it's basically dependent upon the method we select. And then basically on the allocation part, we have our labels which we assign to the nodes. We once it is set aside basically to that label, then only it will go through the location on that. So, if we can, we can set up some selectors on that where node affinity basically allows us to define that a port will go to which node group and which node. Basically, we can define user node affinity. Right? For application scaling, we can use the horizontal pod autoscaler. We can use it based on CPU and memory.
So every time when a new release is happening, we will make sure to have a lower environment where we can test and understand how the system is behaving. If having any issues, we can have a dynamic Java version in CICD, which we can manage. And that can be worked as an environment very well into Jenkins pipeline, which will run on a new version of Java. And then after that, once it's built, it can deploy to the application. We can process everything through a Jenkins CICD pipeline. Let's say it should be compiled first, then unit testing. Any SonarQube scan for vulnerabilities, we need to do it. We need to test it out, then after, we can deploy it.
So basically, in a dev op project, so we created a Terraform for creating all the resources of AWS cloud using Terraform. And that Terraform will be managed for all the teams. Basically, they can create and use it, and we put it into an approval basis, not default approval. This helps us to centrally manage and automate infrastructure in a centralized way. And apart from that, in a Linux environment, we can use UgaritabaaS scripting, which can help us configure automated servers. For deploying any application and doing any automation apart from that, we can have a Jenkins CICD, and we can also use Lambda to do these things.
So for zero downtime, we have several strategies. We basically have deployment strategies which we can use. We have a rolling back strategy, also a strategy. We have a green blue deployment, which helps us in zero downtime when we're deploying an application into Docker.