DRA: structured parameters #4381
The text was updated successfully, but these errors were encountered:
@klueska: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.
@klueska: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]
Hello @pohly 👋, Enhancements team here.
Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.
This enhancement is targeting for stage
Here's where this enhancement currently stands:
For this KEP, we would just want to update the following but it's not required for
The status of this enhancement is marked as
Hello @pohly 👋, 1.30 Docs Lead here.
Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.