Latest

Terraform init on Jenkins Kubernetes agents kept failing with "could not resolve hostname" when fetching terraform modules. Cluster DNS was flaky, so forcing pods to use 8.8.8.8 made it work.

SSH still requires a public key even after enabling password auth? On EC2 Ubuntu, cloud-init might be silently overriding your config.

Connection test from old Jenkins (2.492.2) to a new Kubernetes cluster failed with io.fabric8.kubernetes.client.KubernetesClientException due to Unrecognized field "emulationMajor"; upgrading the Kubernetes plugin fixed it.

A quick test to see how fast a Kubernetes namespace can be recovered after deletion. Using Velero with an S3 backend on a K3s cluster, a demo application namespace was backed up, deleted, and restored. The restore completed successfully, recreating the Deployment, Pod, and Service within seconds.

Emails to [email protected] are auto-assigned via Power Automate to one active engineer in round-robin, creating a Planner task. SharePoint tracks rotation and conversation IDs to prevent duplicates, ensuring clear ownership and timely responses.

A private K3s node on Proxmox VE is accessed from a public VPS via Tailscale. The VPS joins the mesh, and adding its Tailscale IP to K3s tls-san allows kubectl access without exposing port 6443 publicly.

Installing Jenkins on Kubernetes via Helm worked smoothly at first, but after a node restart, the pod became unhealthy during plugin initialization. The init container attempted to re-copy plugins into an already populated persistent volume, causing overwrite prompts and blocking startup.