Resource Request

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

apiVersion: v1

kind: Pod

metadata:

  name: resource-demo-pod

  labels:

    app: resource-demo

spec:

  containers:

  - name: resource-demo-container

    image: nginx:latest

    resources:

      requests:

        memory: "64Mi"

        cpu: "250m"

      limits:

        memory: "128Mi"

        cpu: "500m"


Comments

Post a Comment

Popular posts from this blog

Lesson -2 : Docker & Container D | ctr | nerdctl | crictl

The topic Docker vs containerd is really about understanding how modern container systems are structured. Docker used to be the “all-in-one” tool, while containerd is a lower-level component that Docker itself now relies on. 🐳 What is Docker? Docker is a full platform for building, running, and managing containers. Think of Docker as a complete toolkit : Build container images ( Dockerfile ) Run containers ( docker run ) Manage networks, volumes, etc. CLI + API + ecosystem It’s designed to be developer-friendly and easy to use. ⚙️ What is containerd? containerd is a core container runtime . It handles the essential low-level tasks: Pulling images Managing container lifecycle (start, stop) Handling storage and execution It does not include: Image building tools Fancy CLI for developers High-level orchestration features 🧩 Relationship Between Them Originally, Docker had its own runtime. Later, Docker split things up and now: Docker → uses containerd int...
Read more

etcd Clustering

In a Kubernetes cluster, the etcd database is the primary data store for all cluster state and configuration. In a multi-master setup, ensuring that etcd data is consistently shared across all master nodes is critical for cluster operation. Here’s how this sharing and synchronization of etcd data is managed:   1. etcd Clustering When you have multiple Kubernetes master nodes, etcd is typically set up as a cluster. This means that etcd runs in a distributed mode with multiple etcd instances, which are all part of a single logical etcd cluster. The key features of this setup include: Consensus and Replication : etcd uses the Raft consensus algorithm to manage a distributed cluster. Raft ensures that all etcd instances in the cluster agree on the current state of the data and replicate changes consistently. This means that even if one etcd instance fails, the data remains available and consistent across the remaining instances. Leader Election : Within an etcd cluster, one...
Read more

Configuration file - Locations and Configurations

In a Kubernetes cluster, the master node is responsible for managing the cluster's control plane components. These components include the API server, scheduler, controller manager, and etcd (the cluster's key-value store). Configuration files for these components are typically found in various locations on the master node. Here's an overview of some common configuration files and their locations: How do you see your kube-api server in your existing cluster. It depends on how you setup your cluster. If you set it up with Kubeadm tool. Kubeadm deploys the kupe-api server as a Pod  Location: /etc/kubernetes/manifests/kube-apiserver.yaml In a non kube admin setup you can inspect the kube-api service  cat /etc/systemd/system/kube-apiservice.service kube-apiserver: If kube-apiservers is installed using kubeadm tool Location: /etc/kubernetes/manifests/kube-apiserver.yaml Description: The kube-apiserver is the Kubernetes API server that exposes the Kubernetes API. It is the fron...
Read more