Runs the paved road: clusters, CI runners, deployment tooling and the guardrails that keep production safe to change. https://anonycoders.github.io/signpost-sample/teams/devops/ 2026-09-14T00:00:00.000Z DevOps https://anonycoders.github.io/signpost-sample/streamlines/devops/secret-scanning/#update-2026-09-14-push-protection-is-on-for-the-20-busiest 2026-09-14T00:00:00.000Z Priya Raman

If a push is blocked, the message names the file and line. Rotate the credential first, then remove it from the commit — do not just force-push over it, because the secret is already in the reflog. Rolling out to the remaining repositories through October and November.

<p><strong>Action required · Secret scanning and push protection</strong></p><p>If a push is blocked, the message names the file and line. Rotate the credential first, then remove it from the commit — do not just force-push over it, because the secret is already in the reflog.</p> <p>Rolling out to the remaining repositories through October and November.</p> https://anonycoders.github.io/signpost-sample/streamlines/devops/kubernetes-1-31-upgrade/#update-2026-09-10-production-clusters-upgrade-from-1-october 2026-09-10T00:00:00.000Z Jana Okafor Milan Petrovic

Takes effect 1 October 2026. Production upgrades run in three waves starting 1 October. Any workload still declaring networking.k8s.io/v1beta1 Ingress objects will fail to deploy once its cluster is upgraded. Run kubectl deprecations --context <your-cluster> to see whether you are affected. The migration guide has the before-and-after manifests. What you need to do: (1) Run kubectl deprecations --context <your-cluster> against every cluster your team owns. (2) Move any v1beta1 Ingress objects to networking.k8s.io/v1, using the before-and-after manifests. (3) Tell us in #devops if you cannot make 1 October, before the waves start.

<p><strong>Breaking · Kubernetes 1.31 upgrade</strong> — takes effect 1 October 2026</p><p>Production upgrades run in three waves starting <strong>1 October</strong>. Any workload still declaring <code>networking.k8s.io/v1beta1</code> Ingress objects will fail to deploy once its cluster is upgraded.</p> <p>Run <code>kubectl deprecations --context &lt;your-cluster&gt;</code> to see whether you are affected. The migration guide has the before-and-after manifests.</p> <p><strong>What you need to do</strong></p><ul><li>Run <code>kubectl deprecations --context &lt;your-cluster&gt;</code> against every cluster your team owns.</li><li>Move any v1beta1 Ingress objects to <code>networking.k8s.io/v1</code>, using the <a href="https://github.com/example-org/devops-runbooks/blob/main/k8s-1-31.md">before-and-after manifests</a>.</li><li>Tell us in #devops if you cannot make 1 October, before the waves start.</li></ul> https://anonycoders.github.io/signpost-sample/streamlines/devops/jenkins-pipelines/#update-2026-09-08-38-pipelines-still-to-migrate-before-the-march 2026-09-08T00:00:00.000Z Milan Petrovic

We will contact owning teams individually from October. If your pipeline is on the list and you think it should simply be deleted, tell us — that is often the right answer for pipelines nobody has run this year.

<p><strong>Action required · Jenkins pipelines</strong></p><p>We will contact owning teams individually from October. If your pipeline is on the list and you think it should simply be deleted, tell us — that is often the right answer for pipelines nobody has run this year.</p> https://anonycoders.github.io/signpost-sample/streamlines/devops/kubernetes-1-31-upgrade/#update-2026-09-01-all-staging-clusters-are-running-1-31 2026-09-01T00:00:00.000Z Jana Okafor Milan Petrovic

Staging has been stable for two weeks. This is the window to catch problems before the production waves begin.

<p><strong>Info · Kubernetes 1.31 upgrade</strong></p><p>Staging has been stable for two weeks. This is the window to catch problems before the production waves begin.</p> https://anonycoders.github.io/signpost-sample/streamlines/devops/secret-scanning/#update-2026-06-15-scanning-runs-in-report-only-mode-across-every 2026-06-15T00:00:00.000Z Priya Raman

No pushes are blocked yet. Findings go to the owning team's channel so you can start rotating without a deadline hanging over you.

<p><strong>Info · Secret scanning and push protection</strong></p><p>No pushes are blocked yet. Findings go to the owning team&#39;s channel so you can start rotating without a deadline hanging over you.</p> https://anonycoders.github.io/signpost-sample/streamlines/devops/github-actions-runners/#update-2026-06-01-runners-are-generally-available-and-are-now-the 2026-06-01T00:00:00.000Z Milan Petrovic

Capacity has been stable through three months of rollout. New repositories created from the golden path templates get runner access automatically.

<p><strong>Info · Self-hosted GitHub Actions runners</strong></p><p>Capacity has been stable through three months of rollout. New repositories created from the golden path templates get runner access automatically.</p> https://anonycoders.github.io/signpost-sample/streamlines/devops/kubernetes-1-31-upgrade/#update-2026-03-02-upgrade-plan-agreed-work-has-started 2026-03-02T00:00:00.000Z Jana Okafor Milan Petrovic

Upgrade plan agreed, work has started

<p><strong>Info · Kubernetes 1.31 upgrade</strong></p> https://anonycoders.github.io/signpost-sample/streamlines/devops/jenkins-pipelines/#update-2026-02-16-jenkins-is-deprecated-move-to-github-actions 2026-02-16T00:00:00.000Z Milan Petrovic

No new pipelines will be created on Jenkins. Existing ones keep running until 31 March 2027, after which the servers are switched off.

<p><strong>Action required · Jenkins pipelines</strong></p><p>No new pipelines will be created on Jenkins. Existing ones keep running until <strong>31 March 2027</strong>, after which the servers are switched off.</p> https://anonycoders.github.io/signpost-sample/streamlines/devops/github-actions-runners/#update-2026-02-16-start-migrating-your-pipelines-jenkins-switches 2026-02-16T00:00:00.000Z Milan Petrovic

Migration is self-service and most pipelines take under a day. Book time with us in #devops if yours is unusual.

<p><strong>Action required · Self-hosted GitHub Actions runners</strong></p><p>Migration is self-service and most pipelines take under a day. Book time with us in <code>#devops</code> if yours is unusual.</p>