Serverless computing is revolutionizing the way we build and deploy applications. With serverless architecture, you don’t need to manage servers or infrastructure, allowing you to focus on writing code and delivering features. Google Cloud Functions is a popular serverless platform that allows developers to deploy functions that automatically scale with usage. In this blog post, we’ll guide you through the process of deploying a Python serverless app, an ASCII art generator, using Google Cloud Functions.
If you prefer to follow video tutorial, check out my YouTube channel tutorial:
As containerized applications continue to rise in popularity, ensuring their security becomes more and more crucial. With Kubernetes, you have a powerful tool for managing containers, but it doesn’t necessarily provide all the security features you need out of the box. That’s where Falco comes in.
Falco is an open-source container security tool that monitors your Kubernetes cluster in real-time and alerts you of any suspicious activity. In this guide, we’ll walk you through setting up Falco on your Kubernetes cluster and discuss its main benefits.
Install Falco on Your Kubernetes Cluster
There are few methods you can install Falco, details can be found in the official documentation: installation or directly on K8s: deployment. The easiest way to install Falco on your Kubernetes cluster is using Helm. Helm is a package manager for Kubernetes that makes it easy to install and manage applications.
In this blog entry I will briefly explain what projects are, and why do you need (and have) at least one in your own GCP (Google Cloud Platform) Console. To understand what projects are, let’s start with the GCP resource. Resources are the fundamental components of all GCP services. Your Compute Engine VM Instance is a resource, your Cloud Storage bucket is a resource, Your VPC Network is a resource. If you prefer the video, check out my YouTube screen-cast:
All those resources are organized, or in other words, parented, by projects. To learn more, continue reading this blog entry.