标签：#upgrade

Summary The OpenBSD project released 7.9 of their OS on 19 May 2026, as their 60th release 💫 What's New | Changelog This post shows how to upgrade OpenBSD 7.8 to 7.9. The steps are based on their official guide with appreciation to them. Tutorial Here is a step-by-step guide with a set of command-lines to run. 🌷 🐡 🌅 1. Pre-upgrade: Validate and customize The official tutorial includes Before using any upgrade method section. Using sysupgrade is usually a good choice. Validate available disk size /usr should be greater than 1.1GB. $ df -h Filesystem Size Used Avail Capacity Mounted on (...) /dev/sd0e 7.8G 1.8G 5.6G 25% /usr OK :) Validate compatibility with the current usage See Configuration and syntax changes and Special packages . The latter this time includes PostgreSQL major update to 18.1 . Backups (Optional) You might have to create some backups. Customize upgrade (Optional) This step is just for reference, skippable with standard upgrade. /auto_upgrade.conf is available as the response file. Of course, you can skip this and go next if it's unnecessary. The default behavior is sufficient in most cases. Well, the OpenBSD manual page on autoinstall says: If either /auto_install.conf or /auto_upgrade.conf is found on bsd.rd 's built-in RAM disk, autoinstall behaves as if the machine is netbooted, but uses the local response file. In case both files exist, /auto_install.conf takes precedence. The whole example of /auto_upgrade.conf is like: Location of sets = disk Pathname to the sets = /home/_sysupgrade/ Set name(s) = -x* Set name(s) = +xbase* Set name(s) = -game* Set name(s) = done Directory does not contain SHA256.sig. Continue without verification = yes In this case, x sets except xbase and game are excluded. Also, /upgrade.site can be applied. 2. Upgrade with sysupgrade OK. You must be ready. * Caution: The command below, sysupgrade , is unable to stop once it is run. Let's just run it, if ready: $ doas sysupgrade It will print out like this: Fetching from ht

I believe Angular upgrades have become much smoother these days. Most of the time, a simple ng update is enough to move to the latest version. Instead, I spent hours chasing errors that looked completely unrelated to the real problem 😭 After upgrading the project to Angular 21, I started seeing errors like these: Cannot find module '@angular/material/chips' Cannot find module '@angular/material/dialog' Then another one appeared: Error: The current version of "@angular/build" supports Angular ^19... but detected Angular version 21.x instead. At first, it looked like Angular Material wasn't installed correctly but i think the actual issue was a version mismatch inside the project. Some packages had already been upgraded to Angular 21: @angular/core @angular/common @angular/material But the build system was still using: @angular-devkit/build-angular@19 Since Angular's build tools are tightly coupled with the framework version, the compiler started producing misleading errors. The build pipeline was the problem. The Commands That Helped I used these commands: npm ls @angular-devkit/build-angular npm explain @angular-devkit/build-angular They showed that my project was still resolving Angular 19's build package. That was the clue I needed and than I verified that every Angular package was using the same major version. Then I cleaned the project completely: rm -rf node_modules rm package-lock.json npm cache clean --force npm install It takes time usually.(and I did it several times cause Im failed 😃) Finally, I confirmed that all Angular packages were aligned before building again.

Introduction One of the common tasks performed by DevOps Engineers is upgrade of their organization's Kubernetes Cluster at least once every 3 months as Kubernetes release newer version while maintaining on the last 3 released versions. For instance, if the newest version is v1.34, the supported versions would be v1.34, v1.33 & v1.32. Hence, the need to understand how this upgrade process can be achieved with zero downtime. Prerequisites: Cordon your Nodes: This simply means making your nodes unschedulable. No new deployments would be scheduled on the node. Review and understand the change logs in the release notes - Ensure that the change logs or updated components won't affect your production environment. Kubernetes upgrade are irreversible - You can't downgrade your cluster after an upgrade. A fresh installation would be required in the event of an issue with the upgraded version. Hence Lower Level Environment Test (Unit, Staging or Pre-Production) - Given that Kubernetes upgrades are irreversible, always test the newer version and allow monitoring for about 2-weeks before production cluster upgrade. Control Plane & Nodes should be on the same versions. Cluster Auto-Scaler: If you are using this feature within your Kubernetes environment, ensure that it is on the same or compatible version with your control plane to avoid issues during the cluster upgrade. IP Addresses: Make available at least 5 IP addresses within the cluster subnet. Kubelet: This component should also match the version of your control plane before the upgrade. What are the actual upgrade processes Control Plane Upgrade: If using the Managed Kubernetes Cluster (EKS, AKS, GKS), the Cloud Company will take care of managing the control plane. However, upgrade of the cluster doesn't happen automatically. Hence, you will be required to action this via the CLI, UI or EKSCLI etc. Node Group or Data Plane Upgrade: Managed Node Groups - This is easier because you can use the rollout deployment approach,