It is safe to say that it’s a future-proof move for your career to understand more about cloud technologies.

There are many reasons to love Kubernetes. It’s open source. It’s incredibly scalable and flexible. And it turns out to be a great way to deploy hybrid cloud and multi-cloud workloads.

Stack Overflow’s 2021 Developer Survey found that 54% of developers use AWS, yet only 7% use Terraform.

In simpler times, IT operations had the responsibility to configure and deploy new infrastructure, mostly via command line interface (CLI) and scripts. Today, even those with the most advanced command line prowess cannot keep up with the scalability and agility demands of companies building and deploying infrastructure in the cloud.

Speed is the name of the game for developers. That’s why security isn’t always a top priority for them—it’s seen as a slowdown or blocker for developers whose performance depends on their velocity.

Kubernetes is a powerful tool with enough settings to deploy a performant, scalable, and reliable cloud native application. There are also enough settings so that it’s hard to keep all security and compliance best practices straight.

How to deploy a CGE Instance with Gitlab CI using Terraform and Ansible

No, this isn’t another post about the Secure Development Lifecycle. This is a practical post on why and how to address cloud security at each step of the infrastructure development lifecycle, from infrastructure as code in your IDE to running cloud resources.

Helm charts are an easy way to package, version and deploy applications on Kubernetes. They can be used to deploy application services or even Kubernetes components and tools.

Cloud configurations change. All the time. It’s futile to imagine web app development without a constant stream of configuration changes in order to adopt new technologies, release new features, and support new business requirements.