What is Podman?? Podman is a daemon-less container engine for developing, managing, and running OCI Containers on your Linux System. Containers can either be run as root or in rootless mode. Docker VS Podman Daemonless - Docker is built on top of runC runtime container runtime, which runs a docker daemon to execute tasks. Podman is light-weight and doesn’t require an always running instance for running containers, It is directly using the runC runtime container.
1.0 Introduction There are so many monitoring services out there to monitor Linux servers and IoT Devices like Raspberrypi’s. So here, I mention the two leading systems to monitor raspi or any other Linux server. Prometheus + Node Exporter + Grafana InfluxDB + Telegraf + Grafana NOTE: So before moving further, first, I let introduce you to what these monitoring tools are and how they differ from each other: 1.
Marking Points Always keep clean & organized your working environment Small improvements makes a big difference ( Always take a baby steps ) Think: with the same steps you will end up with the same results. but with better habits and routine, anything is possible ( so why not to try new things, if things worked for you adopt it, otherwise drop it ) Break large problems into chunks ( Gradually improve your skills by 1 Percent and after some time you will see a significant increase when you put them all together )
1.0 Kubernetes Volumes: Attaching disk storage to containers Kubernetes volumes are a component of a pod and are thus defined in the pod’s specification much like containers. They aren’t a standalone Kubernetes object and cannot be created or deleted on their own. A volume is available to all containers in the pod, but it must be mounted in each container that needs to access it. In each container, you can mount the volume in any location of its filesystem
1.1 What is Service Discovery A Kubernetes Service is a resource you create to make a single, constant point of entry to a group of pods providing the same service. Each service has an IP address and port that never change while the service exists. Clients can open connections to that IP and port, and those connections are then routed to one of the pods backing that service. This way, clients of a service don’t need to know the location of individual pods providing the service, allowing those pods to be moved around the cluster at any time.