Remove rollouts from kpt as rollouts implement similar functionality to Porch

[liamfallon]

Rollouts are an "alpha" concept in kpt for deploying workloads to clusters. However, the recommended approach for deploying workloads in kpt is using Porch from the Nephio Project. This PR removes rollouts from kpt as they are not supported and will not be developed any further.

Removing rollouts resolves the backlog issues that have been raised on rollouts below:
Fixes: #4403
Fixes: #3688
Fixes: #3777
Fixes: #3767
Fixes: #3773
Fixes: #3885
Fixes: #3778
Fixes: #3886
Fixes: #3835
Fixes: #3858
Fixes: #3839
Fixes: #3855
Fixes: #3862
Fixes: #3836
Fixes: #3854
Fixes: #3866
Fixes: #3775
Fixes: #3297
Fixes: #3119
Fixes: #3343
Fixes: #3351

[netlify]

✅ Deploy Preview for kptdocs ready!

Name	Link
🔨 Latest commit	08c9bfc
🔍 Latest deploy log	https://app.netlify.com/projects/kptdocs/deploys/699c2264f8b04f0008674a89
😎 Deploy Preview	https://deploy-preview-4402--kptdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR removes the rollouts functionality from kpt, as it is an alpha/deprecated feature being replaced by Porch from the Nephio Project. The PR includes extensive file deletions of rollouts-related code, removal of rollouts dependencies, and some code modernization updates (using any instead of interface{}, using slices and maps packages).

Changes:

• Complete removal of the rollouts/ directory and all rollouts-related functionality
• Removal of rollouts commands from the alpha CLI
• Code modernization: replacing interface{} with any, using slices.Contains() and maps.Copy()
• Addition of a new boilerplate file at scripts/boilerplate.go.txt

Reviewed changes

Copilot reviewed 143 out of 146 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
rollouts/* (deleted)	Entire rollouts directory removed including API, controllers, pkg, config, scripts
commands/alpha/rollouts/* (deleted)	Rollouts CLI commands removed
commands/alpha/alphacmd.go	Rollouts command registration removed
go.mod/go.sum	Rollouts and related dependencies removed
thirdparty/cmdconfig/commands/runner/runner.go	Refactored to use slices.Contains
pkg/test/porch/cluster.go	kubectl command modified (contains bug)
pkg/test/runner/runner.go	Updated to use strings.SplitSeq
pkg/status/poller.go	Removed RolloutStatusReader
pkg/status/rollout.go (deleted)	Rollout status functionality removed
scripts/boilerplate.go.txt (added)	New boilerplate file
Various files	Code modernization: interface{} → any, using slices/maps packages

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 142 out of 145 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 142 out of 145 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dosubot]

Documentation Updates

2 document(s) were updated by changes in this PR:

_index

View Changes

@@ -29,7 +29,7 @@
 * package customization with _guardrails_
 * evaluation of functions on package contents
 * approval flow to publish a change to a configuration package
-* deployment and rollouts
+* deployment
 
 Package Orchestration enables [workflows](../02-concepts/#workflows)
 similar to those supported by the kpt CLI, but makes them available as a

porch-user-guide

View Changes

@@ -1,6 +1,8 @@
 # Porch User Guide
 
 This document is focused on using Porch via the `kpt` CLI.
+
+Porch, from the [Nephio Project](https://github.com/nephio-project/porch), is the recommended approach for deploying workloads in kpt.
 
 Installation of Porch, including prerequisites, is covered in a
 [dedicated document](guides/porch-installation.md).

^{How did I do? Any feedback?}