From 21ca24047a519d8c29a6db2463f3379951d15aec Mon Sep 17 00:00:00 2001 From: Puskar Basu Date: Thu, 13 Aug 2026 14:08:44 +0530 Subject: [PATCH] Add blog post for SCOS upgrade authentication fix --- blog/2026/08-13-scos-upgrade-auth-fix.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 blog/2026/08-13-scos-upgrade-auth-fix.md diff --git a/blog/2026/08-13-scos-upgrade-auth-fix.md b/blog/2026/08-13-scos-upgrade-auth-fix.md new file mode 100644 index 0000000..5a7e4b0 --- /dev/null +++ b/blog/2026/08-13-scos-upgrade-auth-fix.md @@ -0,0 +1,23 @@ +--- +title: "[Resolved] OKD SCOS upgrades failing with authentication required" +authors: ["pskrbasu"] +date: 2026-08-13 +--- + +If you've been hitting `authentication required` errors when trying to upgrade your OKD SCOS cluster, this has been fixed. Users have confirmed upgrades are working again. + +## What happened + +The OKD SCOS release payload images on `registry.ci.openshift.org` required authentication to pull, but end-user clusters don't have credentials for this registry. This meant any upgrade attempt would fail with `ImagePullBackOff` / `authentication required`, regardless of the version. + +## What was fixed + +The image-puller rolebinding for the OKD namespaces has been updated to allow unauthenticated pulls, matching how it already works for OCP. + +Fix: [openshift/release#83361](https://github.com/openshift/release/pull/83361) + +## What to do + +If your upgrade was stuck, retry it — it should work now without any changes on your end. + +Tracking issue: [okd-project/okd#2347](https://github.com/okd-project/okd/issues/2347)