Kalyan G.

I worked as a DevOps engineer. For me, it's not Devops it's the dev sec Ops, which is just part of it. So, I always like to use myself as a hobby because you need to propose dev sec ops practice within two principles. Let me do the tech stack first and then I'll start calling primary across both cloud providers AWS and Azure, Google, not so much so obviously maximum time, but not so much as often. We don't have major clients who are essentially leveraging, to a large extent as much as they are with integration and Azure. Look at most of the services everything from a Vpc and Elb through eks. And I'll come to containers in a moment. My areas of expertise are both architecture and implementation so architecture concerns how should our new application clean tubes and tie workflow, through our CI CD pipelines and then essentially get deployed in an iterated manner, through different environments, as it makes certain production in a secure safe manner with finding things everywhere from network security to identity and access management models. That's the tech stack mostly and that includes things like Ansible which includes containers Kubernetes and Docker it includes cloud formation of more importantly terraform includes version control, I finally work with git. I worked Jenkins using variable ci, I'm going through this fact and those are the ones that have popped into my mind recently has now come to the role. I'm essentially working with you to help you set up your team how you set up your project structure have you come on to a CI CD pipeline in a safe manner, create roles for developers, etc