Vitalie Procopan’s Devops Blog

K8s Clean Evicted Pods

2026-02-16T00:00:00+00:00

To clean evicted pods run:

kubectl get pods -A -o json \
| jq -r '.items[]
  | select(.status.reason=="Evicted")
  | "\(.metadata.namespace) \(.metadata.name)"' \
| while read ns pod; do
    kubectl delete pod -n "$ns" "$pod" --grace-period=0 --force
  done

How To Add Kubespray Node

2026-01-26T00:00:00+00:00

to add a node use:

ansible-playbook -i /inventory/inventory.ini --private-key /root/.ssh/id_ed25519 scale.yml --limit="node6,kube_control_plane" --become -vvv

Patch Pod

2025-12-19T00:00:00+00:00

Remove probes at runtime

kubectl patch deploy pihole -n pihole --type json -p='[
  {"op":"remove","path":"/spec/template/spec/containers/0/livenessProbe"},
  {"op":"remove","path":"/spec/template/spec/containers/0/readinessProbe"}
]'

Dns

2025-12-15T00:00:00+00:00

to view DNS settings in ubuntu, enter the command:

resolvectl

Winget

2025-12-12T00:00:00+00:00

WinGet: The Windows Package Manager

WinGet is Microsoft’s official package management tool for Windows. It provides:

CLI (Command Line Interface)
PowerShell modules
COM API (Component Object Model Application Programming Interface)

Learn more in the official WinGet documentation.

Kubespray

2025-12-01T00:00:00+00:00

🐳 Run Kubespray container

docker run --rm -it \
  --mount type=bind,source="$(pwd)"/inventory/sample,dst=/inventory \
  --mount type=bind,source="${HOME}"/.ssh/id_ed25519,dst=/root/.ssh/id_ed25519 \
  quay.io/kubespray/kubespray:v2.29.0 bash

⚙️ kube-vip Configuration

You will edit:

inventory/sample/group_vars/k8s-cluster/addons.yml
inventory/sample/group_vars/k8s-cluster/k8s-cluster.yml

🟦 addons.yml — Enable kube-vip

# Enable kube-vip for API server load balancing
kube_vip_enabled: true

# Virtual IP for your Kubernetes control-plane
kube_vip_address: 192.168.100.10

# API Server Load Balancer
loadbalancer_apiserver:
  address: ""
  port: 6443

# Interface where the VIP will be bound
kube_vip_interface: eth0

# Enable ARP mode (Layer2)
kube_vip_arp_enabled: true
kube_vip_controlplane_enabled: true

# Service LoadBalancer functionality (disabled)
kube_vip_services_enabled: false

# DNS resolution mode
kube_vip_dns_mode: first

# Misc kube-vip options
kube_vip_cp_detect: false
kube_vip_lb_fwdmethod: local
kube_vip_enable_node_labeling: false

# Run kube-vip pod in hostNetwork with NET_ADMIN capability
kube_vip_pod_hostnetwork: true
kube_vip_pod_capabilities:
  add:
    - NET_ADMIN

🔧 k8s-cluster.yml — Required ARP Fix

kube-vip requires strict ARP mode in kube-proxy.

kube_proxy_strict_arp: true

✔️ Summary

This setup:

Enables kube-vip as the control-plane load balancer
Uses Layer2 (ARP) mode
Assigns a static VIP: 192.168.100.10
Ensures kube-proxy is correctly configured (strict_arp: true)
Runs kube-vip with the necessary NET_ADMIN capability

Everything is now ready for:

ansible-playbook -i /inventory/inventory.ini --private-key /root/.ssh/id_ed25519 cluster.yml

Upgrade Linux Different Commands

2025-11-25T00:00:00+00:00

difference between upgrade -y and dist-upgrade -y

apt-get update updates the list of available packages and their versions, but it does not install or upgrade any packages.

apt-get upgrade actually installs newer versions of the packages you have. After updating the lists, the package manager knows about available updates for the software you have installed. This is why you first want to update.

apt-get dist-upgrade in addition to performing the function of apt-get upgrade, also intelligently handles changing dependencies with new versions of packages and will attempt to upgrade the most important packages at the expense of less important ones if necessary. Thus, the apt-get dist-upgrade command may actually remove some packages in rare but necessary instances.

Apt Upgrade Only A Package

2025-11-18T00:00:00+00:00

If you want apt to update ONLY the Jenkins package (and not upgrade the whole system), use:

✅ 1. Update package index

You must always update sources first:

sudo apt update

✅ 2. Upgrade ONLY the Jenkins package

sudo apt install --only-upgrade jenkins

This will:

NOT install new packages
NOT update anything else
ONLY upgrade the jenkins package if an update exists

🔍 Check version afterwards:

dpkg -l | grep jenkins

📝 If Jenkins is installed via repo (recommended)

Make sure your /etc/apt/sources.list.d/jenkins.list is correct:

deb https://pkg.jenkins.io/debian-stable binary/

Then run the upgrade command above.

⛔ If you want to prevent other packages from upgrading

You can hold the rest:

sudo apt-mark hold '*'
sudo apt-mark unhold jenkins

But normally unnecessary — the --only-upgrade flag is enough.

Cloud Init

2025-11-15T00:00:00+00:00

Perfect — here is the clean, guaranteed-working, official Ubuntu 24.04 Cloud-Image + cloud-init (NoCloud) + Virt-Manager setup.

This is the method Ubuntu itself recommends for KVM/QEMU. Zero installer. Zero GRUB. Zero autoinstall pain.

This will work 100%.

✅ OVERVIEW (what you will get)

A VM that:

Boots instantly (no installer)
Uses cloud-init like AWS / Azure / Proxmox
Has your user vprocopan
Has your SSH key installed
Has qemu-guest-agent enabled
Is reproducible, template-ready, cloud-ready

And created entirely using cloud image + NoCloud seed.

🚀 STEP 1 — Download Ubuntu 24.04 cloud image

mkdir ~/cloudvm
cd ~/cloudvm

wget https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img

This file is the actual OS image, no installer.

🚀 STEP 2 — Resize the VM image

Let’s make it 50GB total disk:

qemu-img resize noble-server-cloudimg-amd64.img 50G

🚀 STEP 3 — Create cloud-init config

3.1 `user-data`

nano user-data

Paste:

#cloud-config
users:
  - name: user
    groups: [ sudo ]
    shell: /bin/bash
    sudo: ALL=(ALL) NOPASSWD:ALL
    ssh_authorized_keys:
      - ssh-ed25519 XXX

package_upgrade: true

packages:
  - qemu-guest-agent

runcmd:
  - systemctl enable qemu-guest-agent
  - systemctl start qemu-guest-agent

3.2 `meta-data`

nano meta-data

instance-id: cloudimg-001
local-hostname: ubuntu-cloud

🚀 STEP 4 — Create the NoCloud seed image

This is the magic piece from the official cloud-init QEMU tutorial.

genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data

IMPORTANT: The volume label must be cidata (lowercase). This is how NoCloud datasource detects it.

🚀 STEP 5 — Create the VM in Virt-Manager

🔹 Add VM manually:

1. Create new VM → “Import existing disk image” Select:

noble-server-cloudimg-amd64.img

OS type:

Ubuntu 24.04 (or Generic Ubuntu)

2. Choose Q35 + UEFI (recommended) Under Overview →

Chipset: Q35
Firmware: UEFI (OVMF)

3. Add the cloud-init seed disk Add Hardware → Storage → “Select or create custom storage” → choose:

seed.iso

IMPORTANT: Set:

Device type: Disk
Bus: SCSI or VirtIO

(Cloud-init sees disks, not CDROMs.)

4. Ensure the boot order boots only from the main disk NOT from seed.iso.

🚀 STEP 6 — Boot the VM

During first boot:

cloud-init will detect NoCloud (seed.iso)
apply user-data
create user vprocopan
add SSH key
enable qemu-guest-agent
resize disk to full 50GB

You can watch progress:

sudo tail -f /var/log/cloud-init-output.log

Check status:

cloud-init status --wait
cloud-init status --long

🚀 STEP 7 — SSH into the VM

Get the VM IP from virt-manager or inside VM:

ip a

Then SSH:

ssh vprocopan@

Your key works instantly.

🎉 DONE

You now have:

A real cloud-image VM
No installer needed
Full cloud-init support
Perfect for DevOps work
Runs instantly
Repeatable
Zero GUI interaction

Git Ignore Cached Rm

2025-11-09T00:00:00+00:00

git rm -r –cached .idea

This removes .idea from Git index only, not your disk. (–cached = keep local, untrack in repo.)