CI/CD seems to be simple. But let's take a step back, and look at it from a helicopter view. Let's think about the design CI/CD processes for the project, team, even organization. Let's go through "architecture of CI/CD". What areas should we cover? How to talk with Stakeholders about CI/CD when we design the bloodstream of DevOps driven Organization? During this presentation we will identify the painpoints and talk about the framework which helps to better understand the challenge. Oh, and one last thing. This framework is like a "babel fish", use it to talk to all stakeholders and engineers!

A story about a girl, who moved to Bengaluru to explore her career. That landed her in the DevOps world. Yes, that’s me. I started as an electronics engineer where I was managing an entire production floor that manufactures electronics products. With no prior experience in an IT firm, I quit my current electronics job and started discovering options to join an IT firm. That’s when I got to know about the DevOps world that made me curious and wanted to know more about this world and how it actually works. I started searching about the DevOps lifecycle, slowly I got to know about various DevOps tools that are used. My talk is all about my journey toward DevOps. I would be explaining different DevOps tools like Kubernetes, Docker, Git, and various cloud platforms like Azure, AWS, and GCP. Also, I would like to share some insights on things to know before starting your DevOps career.

DevOps has been growing in popularity recently, particularly in (software) companies that want to reduce their lead time to be measured in days/weeks instead of months/years.

But, what about the secrets? The current trend increases the number of secrets required to run our services. This places a new level of maintenance on our security teams. How can we share and manage the secrets(certificates, passwords, SSH, API keys) for our services in this dynamic scenario, where instances are started automatically, where there are multiple instances of the same services for scalability reasons? Are you keeping up?

How are these secrets managed in GitOps?

Come to this session to learn how to keep secrets secret for the whole lifecycle of the application, from the early beginning when you start developing it until the application is up and running in the Kubernetes cluster.

Nowadays DevOps Engineers love different things about Infrastructure as Code. Be declarative when building and automating infrastructure, and perform the deployment through a GitOps deployment.

What is GitOps? It is a way of managing the infrastructure and application so that the system is described declaratively and version controlled. It has an automated process that ensures that the deployed environment matches the state specified in a repository.

Is it cool, am I right?! But, what about Kubernetes? Yes, we have the excellent YAML files, but wouldn't it be awesome to declare the state into a Git repository and wait for the cluster to automatically update itself instead of manually doing it?

Here is the newly graduated CNCF project Flux! It allows you to declare, and automate your Kubernetes cluster by simply pushing code to a Git repository and letting K8s do the rest of the tedious work.

I spent 90 days walking through some of the key areas of DevOps documenting my journey. Starting with What is and Why do we use DevOps? This touches on the responsibilities of a role surrounded by DevOps processes and principles. It then goes into hands-on practical examples covering, programming languages, networking, Linux, Containers, Kubernetes, and lots more.

In this session, we will take a look at this learning in public resource that has gained over 10,000 stars on GitHub to date and growing massively fast with contributors actively adding functionality and adding to the resource in so many ways including translating to Chinese.