Helm has recently announced it’s much-awaited version 3 and the server component added in Helm 2, Tiller, is missing. So, now we have a server-less Helm. Helm was highly dependent on the tiller for managing a chart life-cycle into Kubernetes.
Tiller is the tool used by Helm to deploy almost any Kubernetes resource. To do this, by default Helm takes the maximum permission to make changes in Kubernetes. Because of this, anyone who can talk to the Tiller can deploy or modify any resources on the Kubernetes cluster, just like a system-admin. This can cause security issues in the cluster…
Companies have migrated to Kubernetes in production but still, many developers are running the application as dev machine or using tools like Docker Compose for running and testing their application.
As most of the developers don’t need to know Kubernetes fully, we need a way for them to test their application on their local machine by running a single command.
To set up the development environment for the developers, the machine needs a working Kubernetes node, with other tools installed. …
Rook has gotten really popular by becoming a part of Cloud Native foundation and giving a solution for persistent storage on Kubernetes. Rook orchestrates different storage solution, but we would be setting up the ceph solution that has reached its first release.
I will be taking you through the requirements needed to setup rook on GKE, and setting them up.
Step 1. Start a Kubernetes Cluster with the ubuntu image