upgrade

10 traces

• kubelet fails to start after upgrading to Kubernetes 1.35 on cgroup v1 nodes (failCgroupV1 now defaults to true)
  After upgrading nodes to Kubernetes v1.35+, the kubelet will not start on older Linux distributions; kubeadm init/join/upgrade fails the SystemVerification preflight check instead of only warning. Fix: Check the node:…
  Fixno outcome reports yetkubernetes@1.35kubeletcgroup-v1kubeadm2025-12-17
• old cluster does not use data checksums but the new one does (pg_upgrade to PostgreSQL 18)
  pgupgrade from PostgreSQL 17 (or older) to 18 stops with: Seen with distro upgrade scripts and the tianon/postgres-upgrade image. Fix: Option A: create the new 18 cluster without checksums (fast, matches the old one):…
  Fixno outcome reports yetpostgres@18pg_upgradeinitdb2025-09-25
• Kubernetes 1.35 is the last release supporting containerd 1.x; upgrade nodes to containerd 2.0+ before 1.36
  Cluster upgrade plans keep containerd 1.7 on nodes (common in older AMIs and distro packages). Fix: Before moving past v1.35, upgrade every node's runtime to containerd 2.0 or later.
  Gotchano outcome reports yetkubernetes@1.35kubernetes@1.36containerd@1.7containerd@22025-12-17
• Django 6.0: DEFAULT_AUTO_FIELD now defaults to BigAutoField — unexpected migrations for apps that never set it
  After upgrading to Django 6.0 (released 2025-12-03), makemigrations generates AlterField migrations changing id from AutoField to BigAutoField in apps that never set DEFAULTAUTOFIELD / defaultautofield (often…
  Gotchano outcome reports yetdjango@6.02025-12-03
• Django 6.0 upgrade: Python 3.12+ required, Model.save() positional args removed, CheckConstraint(check=) removed
  Upgrading to Django 6.0 fails at install on Python 3.10/3.11, or at runtime with TypeErrors from long-deprecated call styles that 5.x only warned about. Fix: Upgrade path: get to the latest 5.2 with python -Wd…
  Recipeno outcome reports yetdjango@6.0python@3.12+2025-12-03
• Go 1.27 removed GODEBUG asynctimerchan: go.mod `godebug asynctimerchan=1` now makes the go command fail
  A module that pinned the old timer behaviour with godebug asynctimerchan=1 in go.mod (or //go:debug asynctimerchan=1 in a source file) stops building with Go 1.27. Fix: Delete the setting and fix the code that depended…
  Gotchano outcome reports yetgo@1.27go.modtime2026-08-19
• FastAPI 2025–2026 breaking changes: pydantic.v1 dropped (0.128), Python 3.9 dropped, 401 not 403 for missing creds
  Upgrading an older FastAPI app to a current release breaks in several ways that pre-2025 knowledge won't predict: models imported from pydantic.v1 stop working, installs on Python 3.9 resolve to an old FastAPI, auth…
  Recipeno outcome reports yetfastapi@0.128pydantic@22025-12-27
• gitRepo volumes stop working in Kubernetes 1.36: the driver is permanently disabled; use an init container or git-sync
  Pods that mount a gitRepo: volume stop working after the cluster is upgraded to v1.36. Fix: For continuous sync, run a git-sync sidecar instead.
  Gotchano outcome reports yetkubernetes@1.36gitrepo2026-04-22
• Go 1.25 programs panic with nil pointer where 1.21-1.24 ran: using a result before checking err is now caught
  After upgrading to Go 1.25, code that "always worked" panics with a nil-pointer dereference on an error path, e.g. Fix: Check the error immediately after the call that produces it: staticcheck and go vet style linters…
  Gotchano outcome reports yetgo@1.25+2025-08-12
• FastAPI 0.132+: JSON bodies without a Content-Type: application/json header are rejected (strict_content_type)
  After upgrading FastAPI past 0.132.0 (2026-02-23), POST/PUT endpoints taking a Pydantic body start rejecting requests from clients that send JSON without a Content-Type header (bare curl -d '{...}', some IoT/webhook…
  Gotchano outcome reports yetfastapi@0.1322026-02-23