Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks for v1.9 release cycle #11092

Open
29 of 41 tasks
Sunnatillo opened this issue Aug 26, 2024 · 8 comments
Open
29 of 41 tasks

Tasks for v1.9 release cycle #11092

Sunnatillo opened this issue Aug 26, 2024 · 8 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@Sunnatillo
Copy link
Contributor

Sunnatillo commented Aug 26, 2024

Please see the corresponding sections of the role-handbooks for documentation of individual tasks.

Tasks

Notes:

  • Weeks are only specified to give some orientation.
  • The following is based on the v1.9 release cycle. Modify according to the tracked release cycle.

Week 1:

Week 1 to 4:

Week 4:

Week 8:

Week 11 to 12:

Week 12:

Week 13:

  • KubeCon idle week

Week 14:

Week 15:

Week 16:

Week 17:

Continuously:

If and when necessary:

/priority critical-urgent
/kind feature

Reminder!
Add to release notes:

Highlights

Deprecation and Removals Warning

@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 26, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment Aug 26, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment Aug 26, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment from Sunnatillo Aug 26, 2024
@sbueringer
Copy link
Member

/triage accepted

(@Sunnatillo just fyi, I removed the spam)

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 26, 2024
@sbueringer sbueringer added this to the v1.9 milestone Aug 26, 2024
@sbueringer
Copy link
Member

@Sunnatillo fyi, I updated the issue description according to #11088 (mostly to fix the links)

@Sunnatillo
Copy link
Contributor Author

I have fixed the week numbers to align with https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/releases/release-1.9.md

@sbueringer
Copy link
Member

@Sunnatillo Would be great if we can link the PRs to the corresponding sub-tasks in this issue. Just makes it a lot easier to track the ongoing work and ensure nothing is missed

@Sunnatillo
Copy link
Contributor Author

@Sunnatillo Would be great if we can link the PRs to the corresponding sub-tasks in this issue. Just makes it a lot easier to track the ongoing work and ensure nothing is missed

done

@sbueringer
Copy link
Member

sbueringer commented Oct 9, 2024

@Sunnatillo Can you please make a note that we should add something about the following to the release notes of v1.9.0? (please in a public place, e.g. in the description of this issue)

Release notes draft (as of 19th November)

## Highlights

- Bumped to controller-runtime v0.19, k8s.io/* v0.31, controller-gen v0.16
- Improvements to status fields: (#11105)
  - Proposal: [Improving status in CAPI resources](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240916-improve-status-in-CAPI-resources.md)
  - Just a few highlights:
    - Overhaul of our contract documentation: [Provider contracts](https://cluster-api.sigs.k8s.io/developer/providers/contracts)
    - Implemented v1beta2 conditions for core Cluster API objects
    - Huge improvements to `Deleting` conditions of Cluster, KCP, MD, MS and Machines
    - Added `Available` conditions to Cluster, KCP and MD
    - Added `ControlPlaneInitialized`, `ControlPlaneAvailable`, `WorkersAvailable`, `RemoteConnectionProbe`, conditions to Cluster
    - Added `UpToDate` conditions to KCP and MD Machines
    - Added `ScalingUp`, `ScalingDown`, `Remediating`, `MachinesReady`, `MachinesUpToDate` conditions to Cluster, KCP, MD and MS
    - Significantly improved `Available`, `EtcdClusterHealthy` and `ControlPlaneComponentsHealthy` conditions on KCP 
    - Added `Paused` conditions
    - Improved counter fields for Cluster, KCP, MD, MS
    - Added utils and extended patch helper for v1beta2 conditions
- ClusterCache supersedes the now deprecated ClusterCacheTracker (#11272)
- ClusterClass: Support oneOf/anyOf/allOf/not in variable schemas (#10637)
- Improved logging in predicates (#10959 #11239 #11188)
- KubeadmControlPlane: Implement pre-terminate hook for clean Machine Deletion (#11137)
- KubeadmControlPlane: NamingStrategy for Machines (#11123)
- MachineSetPreflightChecks feature got promoted to beta (#11228)
- MachineSet/MachineDeployment: Foreground deletion for MachineDeployments and MachineSets (#11174)
- Machine: Improvements to Node drain:
  - Improve Node drain observability (#11074 #11121): documentation: [Machine deletion process](https://main.cluster-api.sigs.k8s.io/tasks/automated-machine-management/machine_deletions)
  - MachineDrainRules Configurable Machine drain behavior (#11240): Proposal: [MachineDrainRules](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20240930-machine-drain-rules.md)
  - Stop waiting for detachment of volumes belonging to Pods ignored during drain (#11246 #11386)
- As usual, significantly improved e2e test framework & coverage (e.g. #11066 #11333 #10984 #11082 #11212 #11127 #11362)
- New providers in clusterctl: Canonical (#11337), Nutanix (#11135), Vultr (#11091)

## Deprecation and Removals Warning

- API: Deprecated FailureMessage and FailureReason fields (#11317)
- The ClusterCacheTracker component has been deprecated (#11312 #11340), please use the new ClusterCache instead.
  - For more context and examples for how to use it, see [PR: Introduce new ClusterCache](https://github.com/kubernetes-sigs/cluster-api/pull/11247) and the corresponding [issue](https://github.com/kubernetes-sigs/cluster-api/issues/11272)
  - Please note:
    - The DisabledFor option (previously ClientUncachedObjects) is not defaulted to &corev1.ConfigMap & &corev1.Secret anymore, thus it’s now necessary to explicitly set DisabledFor to avoid caching ConfigMaps and Secrets.
    - SecretClient and UserAgent are now mandatory options, please take a look at the corresponding godoc.
  - The `--clustercachetracker-concurrency`, `--clustercachetracker-client-qps` and `--clustercachetracker-client-burst` flags on all core CAPI controllers have been renamed to `--clustercache-concurrency`, `--clustercache-client-qps` and `--clustercache-client-burst`
- The deprecated `--metrics-bind-addr` flag has been removed (#11140)
- Deprecated obsolete `errors` package (#10798)
- Deprecated `ClusterCreateInfraReady` and `ClusterUnpausedAndInfrastructureReady` predicates (#11300)

@sbueringer
Copy link
Member

@Sunnatillo I'm going to use #11092 (comment) to collect further notes for the release notes. Let's just check this post once we write up the release notes closer to the release

@chandankumar4
Copy link
Contributor

Communicated beta release "v1.9.0-beta.0" to providers

List of issues created:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

5 participants
@sbueringer @k8s-ci-robot @chandankumar4 @Sunnatillo and others