How To Use Pre-existing Disk as a K8s Persistent Volume for a GKE Cluster
Managing storage for implementing stateful set solutions is a distinct problem from managing compute instances.
How is it: to live with Kubernetes in production?
Kubernetes’ success is due in no small part to its flexibility and power as a container orchestration system. It can scale virtually indefinitely, providing the backbone for many of the world’s most popular online services. And as a proven open-source solution with a rich ecosystem, it’s easily accessible and simple to set up, whether for personal learning, development, or testing.
When it comes to deploying Kubernetes in production, however, things get a bit more complex. There are numerous aspects you need to consider that cover the full spectrum of critical success factors for an online application, including stability, security, and how you manage and monitor your application once it’s up and running. If you get any of these points wrong, it can be costly.
What are Kubernetes Services?
A Kubernetes service is a logical abstraction for a group of pods in a cluster (all performing the same function).
Since pods are ephemeral, a service enables a group of pods that provide certain functions (web services, image processing, etc.) to be assigned a name and a unique IP address (clusterIP). As long as the service uses this IP address, it does not change. Services also define policies for their access.
How to run your pods without turning gray
In development stages when we debug our Kubernetes deployments or playing with Helm charts we may get stuck with some strange errors.