Merge branch 'main' into patch-1

Author: jplitza

content/en/blog/_posts/2024-12-11-Kubernetes-v1-32-Release/index.md

@@ -1,16 +1,15 @@
 ---
 layout: blog
-title: 'Kubernetes v1.32: {release-name}'
+title: 'Kubernetes v1.32: Penelope'
 date: 2024-12-11
 slug: kubernetes-v1-32-release
 author: >
   [Kubernetes v1.32 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.32/release-team.md)
-draft: true
 ---
 
 **Editors:** Matteo Bianchi, Edith Puclla, William Rizzo, Ryota Sawada, Rashan Smith
 
-Announcing the release of Kubernetes v1.32: {release-name}!
+Announcing the release of Kubernetes v1.32: Penelope!
 
 In line with previous releases, the release of Kubernetes v1.32 introduces new stable, beta, and alpha features.
 The consistent delivery of high-quality releases underscores the strength of our development cycle and the vibrant
@@ -19,14 +18,22 @@ This release consists of 44 enhancements in total.
 Of those enhancements, 13 have graduated to Stable, 12 are entering Beta, and 19 have entered in Alpha.
 
 ## Release theme and logo
-{{< figure src="/images/blog/2024-12-11-kubernetes-1.32-release/k8s-1.32.png" alt="Kubernetes v1.32 logo"
-class="release-logo" >}}
 
-<TODO upload image to static/images/blog/2024-12-11-kubernetes-1.32-release/k8s-1.32.png>
+{{< figure src="k8s-1.32.png" alt="Kubernetes v1.32 logo: Penelope from the Odyssey, a helm and a purple geometric background"
+class="release-logo" >}}
 
-The Kubernetes v1.32 Release Theme is "{release-name}".
+The Kubernetes v1.32 Release Theme is "Penelope".
 
-Kubernetes v1.32's {release-story}
+If Kubernetes is Ancient Greek for "pilot", in this release we start from that origin 
+and reflect on the last 10 years of Kubernetes and our accomplishments: 
+each release cycle is a journey, and just like Penelope, in "The Odyssey",  
+weaved for 10 years -- each night removing parts of what she had done during the day -- 
+so does each release add new features and removes others, albeit here with a much 
+clearer purpose of constantly improving Kubernetes. 
+With v1.32 being the last release in the year Kubernetes marks it's first decade anniversary, 
+we wanted to honour all of those that have been part of the global Kubernetes crew 
+that roams the cloud-native seas through perils and challanges: 
+may we continue to weave the future of Kubernetes together.
 
 ## Updates to recent key features
 
@@ -332,13 +339,6 @@ This removal will allow Kubernetes to handle new hardware requirements and resou
 the complexities of back and forth API calls to the kube-apiserver.
 
 See the enhancement issue [#3063](https://github.com/kubernetes/enhancements/issues/3063) to find out more.
-
-#### Deprecation of gitRepo volume types
-
-The [gitRepo](https://kubernetes.io/docs/concepts/storage/volumes/#gitrepo) volume type is deprecated and will be
-removed in a future release, the deprecation has been executed in light of the security advisory encompassing the
-[CVE-2024-10220](https://nvd.nist.gov/vuln/detail/CVE-2024-10220): Arbitrary command execution through gitRepo volume,
-which was reported publicly in [this issue](https://github.com/kubernetes/kubernetes/issues/128885).
 
 #### API removals
 

content/en/blog/_posts/2024-12-11-Kubernetes-v1-32-Release/k8s-1.32.png

@@ -3,7 +3,6 @@ layout: blog
 title: "Kubernetes v1.32: QueueingHint Brings a New Possibility to Optimize Pod Scheduling"
 date: 2024-12-12
 slug: scheduler-queueinghint
-draft: true
 Author: >
   [Kensei Nakada](https://github.com/sanposhiho) (Tetrate.io)
 ---
@@ -13,7 +12,7 @@ component that selects the nodes on which new Pods run. The scheduler processes
 these new Pods **one by one**. Therefore, the larger your clusters, the more important
 the throughput of the scheduler becomes.
 
-Over the years, the Kubernetes project (and SIG Scheduling in particular) has improved the throughput
+Over the years, Kubernetes SIG Scheduling has improved the throughput
 of the scheduler in multiple enhancements. This blog post describes a major improvement to the
 scheduler in Kubernetes v1.32: a 
 [scheduling context element](/docs/concepts/scheduling-eviction/scheduling-framework/#extension-points)
@@ -128,4 +127,4 @@ Please join us and share your feedback.
 
 ## How can I learn more?
 
-- [KEP-4247: Per-plugin callback functions for efficient requeueing in the scheduling queue](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/4247-queueinghint/README.md)
+- [KEP-4247: Per-plugin callback functions for efficient requeueing in the scheduling queue](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/4247-queueinghint/README.md)

content/en/blog/_posts/2024-12-12-scheduler-queueinghint/index.md

@@ -1,11 +1,10 @@
 ---
 layout: blog
 title: "Kubernetes v1.32: Memory Manager Goes GA"
-date: 2024-11-11
+date: 2024-12-13
 slug: memory-manager-goes-ga
 author: >
   [Talor Itzhak](https://github.com/Tal-or) (Red Hat)
-draft: true
 ---
 
 With Kubernetes 1.32, the memory manager has officially graduated to General Availability (GA),

content/en/blog/_posts/2024-11-11-memory-manager-moves-to-ga/index.md renamed to content/en/blog/_posts/2024-12-13-memory-manager-moves-to-ga/index.md

@@ -1,8 +1,7 @@
 ---
 layout: blog
 title: 'Kubernetes v1.32 Adds A New CPU Manager Static Policy Option For Strict CPU Reservation'
-draft: true
-date: 2024-12-11
+date: 2024-12-16
 slug: cpumanager-strict-cpu-reservation
 author: >
   [Jing Zhang](https://github.com/jingczhang) (Nokia)

content/en/blog/_posts/2024-12-11-cpumanager-strict-cpu-reservation.md renamed to content/en/blog/_posts/2024-12-16-cpumanager-strict-cpu-reservation.md

@@ -1,8 +1,7 @@
 ---
 layout: blog
 title: 'Enhancing Kubernetes API Server Efficiency with API Streaming'
-date: 2024-12-11
-draft: true
+date: 2024-12-17
 slug: kube-apiserver-api-streaming
 author: >
  Stefan Schimanski (Upbound),

content/en/blog/_posts/2024-12-11-api-streaming/index.md renamed to content/en/blog/_posts/2024-12-17-api-streaming/index.md

@@ -1,9 +1,8 @@
 ---
 layout: blog
 title: "Kubernetes 1.32: Moving Volume Group Snapshots to Beta"
-date: 2024-12-11
+date: 2024-12-18
 slug: kubernetes-1-32-volume-group-snapshot-beta
-draft: true
 author: >
    Xing Yang (VMware by Broadcom)
 ---

content/en/blog/_posts/2024-12-11-api-streaming/kube-apiserver-memory_usage.png renamed to content/en/blog/_posts/2024-12-17-api-streaming/kube-apiserver-memory_usage.png

@@ -0,0 +1,26 @@
+---
+title: Compatibility Version For Kubernetes Control Plane Components
+reviewers:
+- jpbetz
+- siyuanfoundation
+content_type: concept
+weight: 70
+---
+
+<!-- overview -->
+
+Since release v1.32, we introduced configurable version compatibility and emulation options to Kubernetes control plane components to make upgrades safer by providing more control and increasing the granularity of steps available to cluster administrators.
+
+<!-- body -->
+
+## Emulated Version
+
+The emulation option is set by the `--emulated-version` flag of control plane components. It allows the component to emulate the behavior (APIs, features, ...) of an earlier version of Kubernetes.
+
+When used, the capabilities available will match the emulated version: 
+* Any capabilities present in the binary version that were introduced after the emulation version will be unavailable. 
+* Any capabilities removed after the emulation version will be available. 
+
+This enables a binary from a particular Kubernetes release to emulate the behavior of a previous version with sufficient fidelity that interoperability with other system components can be defined in terms of the emulated version.
+
+The `--emulated-version` must be <= `binaryVersion`. See the help message of the `--emulated-version` flag for supported range of emulated versions.

content/en/blog/_posts/2024-12-11-volume-group-snapshot-beta.md renamed to content/en/blog/_posts/2024-12-18-volume-group-snapshot-beta.md

@@ -75,6 +75,37 @@ appending a container name to the command, with a `-c` flag, like so:
 kubectl logs counter -c count
 ```
 
+
+### Container log streams
+
+{{< feature-state feature_gate_name="PodLogsQuerySplitStreams" >}}
+
+As an alpha feature, the kubelet can split out the logs from the two standard streams produced
+by a container: [standard output](https://en.wikipedia.org/wiki/Standard_streams#Standard_output_(stdout))
+and [standard error](https://en.wikipedia.org/wiki/Standard_streams#Standard_error_(stderr)).
+To use this behavior, you must enable the `PodLogsQuerySplitStreams`
+[feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
+With that feature gate enabled, Kubernetes {{< skew currentVersion >}} allows access to these
+log streams directly via the Pod API. You can fetch a specific stream by specifying the stream name (either `Stdout` or `Stderr`),
+using the `stream` query string. You must have access to read the `log` subresource of that Pod.
+
+To demonstrate this feature, you can create a Pod that periodically writes text to both the standard output and error stream.
+
+{{% code_sample file="debug/counter-pod-err.yaml" %}}
+
+To run this pod, use the following command:
+
+```shell
+kubectl apply -f https://k8s.io/examples/debug/counter-pod-err.yaml
+```
+
+To fetch only the stderr log stream, you can run:
+
+```shell
+kubectl get --raw "/api/v1/namespaces/default/pods/counter-err/log?stream=Stderr"
+```
+
+
 See the [`kubectl logs` documentation](/docs/reference/generated/kubectl/kubectl-commands#logs)
 for more details.