Skip to content

Commit

Permalink
Added release schedule and KEP of the week
Browse files Browse the repository at this point in the history
  • Loading branch information
sreeram-venkitesh committed Mar 6, 2024
1 parent 850ecae commit fc1d4e9
Showing 1 changed file with 8 additions and 1 deletion.
9 changes: 8 additions & 1 deletion _posts/2024-03-03-update.md
Expand Up @@ -10,7 +10,9 @@ slug: 2024-03-03-update

## Release Schedule

**Next Deadline:**
**Next Deadline: Test Freeze, March 27th**

Code Freeze is [now in effect](https://groups.google.com/a/kubernetes.io/g/dev/c/Y1EJ1HGBPJk/m/mSMClkn4AwAJ?utm_medium=email&utm_source=footer). If your KEP did not get tracked and you want to get your KEP shipped in the 1.30 release, please [file an exception](https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md) as soon as possible.


## Featured PRs
Expand All @@ -37,6 +39,11 @@ As an alpha feature, this is behind the `CustomResourceFieldSelectors` feature g

## KEP of the Week

### [KEP-1610: Container Resource based Autoscaling](https://github.com/kubernetes/enhancements/blob/master/keps/sig-autoscaling/1610-container-resource-autoscaling/README.md)

For scaling pods based on resource usage, the HPA currently calculates the sum of all the individual container's resource usage. This is not suitable for workloads where the containers are not related to each other. This KEP proposes that the HPA also provide an option to scale pods based on the resource usages of individual containers in a Pod. The KEP proposes adding a new `ContainerResourceMetricSource` metric source, with a new `Container` field, which will be used to identify the container for which the resources should be tracked. When there are multiple containers in a Pod, the individual resource usages of each container can change at different rates. Adding a way to specify the target gives more fine grained control over the scaling.

This KEP is in beta since v1.27 and is planned to graduate to stable in v1.30.

## Other Merges

Expand Down

0 comments on commit fc1d4e9

Please sign in to comment.