Control of traffic(ingress/egress) is crucial for a secured Kubernetes cluster. Kubernetes Network Policy provides the offering for so by default but that’s limited to OSI layer 3/4 and is not rich in options. One of the network policy from official doc:

When we don’t need a long running resource like Deployment & ReplicaSet, the option is Job or CronJob in Kubernetes environment. By the name it’s clear CronJob takes a cron type of syntax mentioning when the job is to run. The K8s system itself triggers the job at the specified…

You have a bastion host server which need to run only in office hour(9:00–18:00). There is a compute instance which runs ETL job only on weekend. In the cases like this, keeping the instance turned ON 24 hours will be waste of money and resource. By turning the instance in…

The VPN we are going to mention here: Is free: GCP provides e2-micro instance type for free on US region and we will be utilizing this along with free disk space and egress traffic Can be used for both internal and external traffic: Whether you want to connect to other…

Let’s start with few cases: Do you have to work under private network and host docker images internally? Are you hit by rate limit of docker hub and want to maintain cache of it? Are you hosting docker images on multiple cloud provider(AWS, GCP, Azure etc.) …

Security is always a key concern while running application in any type of system may it be in bare metal or in containerized world. With the increase in number of ephemeral containers, it starts getting harder to keep track of what is running inside each container. …

Kubernetes Job is a workload resource which is created to run a specific type of workload that will exit after a task is completed. A Job keeps track of completion of tasks based on exit code. For example, you want to have a database backup and expect it to complete…

After doing a base Kubernetes cluster setup, the question arises, what if something is going wrong or what if some incident happens? Running a containerized application in the orchestrated environment is step one but monitoring the application and cluster is another important part. Even if we are using a managed…

If we are inside Google Cloud and want to call any GCP services, we prefer using Service Account with Access Scope which makes the identity and API access lot more easier. No burden of handling credential keys but the specific service will have access to another service or API call. …