Release Candidate for Fleet 0.10 / Rancher 2.9

[weyfonk]

With recent refactorings (migration to controller-runtime, #2008, etc), Fleet 0.10 will require special attention.

This includes the following checklist, copied over from #2008:

• Remove packages/fleet/gitjob from rancher/charts' target branch (eg. by editing the PR generated by release-against-charts)
• Check if newly generated index.yaml entry in rancher/charts still includes gitjob as a chart; it should not.
• Check that packages/fleet/fleet/generated-changes no longer contains references to gitjob
• Check that the auto-generated release PR against rancher/charts does not add any docker.io/rancher/gitjob tag entry to regsync.yaml, but generates an entry for docker.io/rancher/fleet-gitjob instead.
• Test installing that Fleet release in Rancher.

[thardeck]

It seems regsync is updated by a label on a pr via a Github action: https://github.com/rancher/charts/blob/dev-v2.9/.github/workflows/regsync-config.yaml
When we submitted Fleet 0.10.0-rc.4 we did not set a label so I have pinged the Maps team on Slack.

[thardeck]

Regarding regsync I got the following information:
We do not use that action in the dev branches. Only in the release branches.

So I guess it should be fine from our side for now.

[manno]

@weyfonk can we close this? :)