Rename TektonScheduler to TektonKueue

[waveywaves]

Changes

Rename the Operator component API from TektonScheduler to TektonKueue,
including TektonConfig.spec.kueue, controller wiring, generated clients and
CRDs, RBAC, Helm and OperatorHub manifests, tests, and documentation.

Retain the deprecated TektonScheduler CRD and TektonConfig.spec.scheduler
field during a compatibility window. Pre-upgrade reconciliation migrates
existing configuration and legacy resources to TektonKueue; explicitly
configured spec.kueue values take precedence.

A local kind upgrade from the pre-rename API verified that queue configuration
is preserved, legacy InstallerSets and resources are removed, both CRDs remain
served, pre-upgrade completes, and the migrated TektonKueue reaches Ready.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Run make test lint before submitting a PR
• Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Release Notes

`TektonScheduler` is deprecated in favor of `TektonKueue`, and
`TektonConfig.spec.scheduler` is deprecated in favor of
`TektonConfig.spec.kueue`. Existing configuration is migrated automatically
during pre-upgrade reconciliation.

Action required: rename scheduler image overrides to `IMAGE_KUEUE_MANAGER` and
`IMAGE_KUEUE_WEBHOOK`.

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign savitaashture after the PR has been reviewed.
You can assign the PR to them by writing /assign @savitaashture in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 25.69%. Comparing base (5a94d1b) to head (448d839).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3809      +/-   ##
==========================================
+ Coverage   25.40%   25.69%   +0.29%     
==========================================
  Files         449      457       +8     
  Lines       23477    23712     +235     
==========================================
+ Hits         5964     6093     +129     
- Misses      16822    16917      +95     
- Partials      691      702      +11     

Flag	Coverage Δ
unit-tests	25.69% <ø> (+0.29%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pramodbindal]

As you mentioned this is breaking change. we need to provide some backward compatibility.

Something like. If you can keep the dummy TektonScheduler for some releases so existing TektonScheduler field does not create any issue and if present we need to move the config to TektonKueue.
This can be done in pre-upgrade Remove the Scheduler so after one release all customers will be moved to TektonScheduler from TektonKueue

[anithapriyanatarajan]

@waveywaves - do we wait until the tekton-kueue project is moved to tektoncd org?

[vdemeester]

@waveywaves - do we wait until the tekton-kueue project is moved to tektoncd org?

for what is worth, it has moved in tektoncd org today 😛

[anithapriyanatarajan]

@waveywaves - do we wait until the tekton-kueue project is moved to tektoncd org?

for what is worth, it has moved in tektoncd org today 😛

Thank you 😄 @waveywaves could you update the import pkg references and components.yaml references. Thank you