Merge pull request #46049 from dipesh-rawat/blog-post-2022-add-author

Update 2022 blog content files to move author details in front-matter
kubernetes · Apr 30, 2024 · 05c5a37 · 05c5a37
2 parents ea4444a + 9cc8cd6
commit 05c5a37
Show file tree

Hide file tree

Showing 65 changed files with 167 additions and 136 deletions.
diff --git a/content/en/blog/_posts/2022-01-07-kubernetes-is-moving-on-from-dockershim.md b/content/en/blog/_posts/2022-01-07-kubernetes-is-moving-on-from-dockershim.md
@@ -3,10 +3,15 @@ layout: blog
 title: "Kubernetes is Moving on From Dockershim: Commitments and Next Steps"
 date: 2022-01-07
 slug: kubernetes-is-moving-on-from-dockershim
+author: >
+  Sergey Kanzhelev (Google),
+  Jim Angel (Google),
+  Davanum Srinivas (VMware),
+  Shannon Kularathna (Google),
+  Chris Short (AWS),
+  Dawn Chen (Google)
 ---
 
-**Authors:** Sergey Kanzhelev (Google), Jim Angel (Google), Davanum Srinivas (VMware), Shannon Kularathna (Google), Chris Short (AWS), Dawn Chen (Google)
-
 Kubernetes is removing dockershim in the upcoming v1.24 release. We're excited
 to reaffirm our community values by supporting open source container runtimes,
 enabling a smaller kubelet, and increasing engineering velocity for teams using

diff --git a/content/en/blog/_posts/2022-01-19-Securing-Admission-Controllers.md b/content/en/blog/_posts/2022-01-19-Securing-Admission-Controllers.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Securing Admission Controllers"
 date: 2022-01-19
 slug: secure-your-admission-controllers-and-webhooks
+author: >
+   Rory McCune (Aqua Security)
 ---
 
-**Author:** Rory McCune (Aqua Security)
-
 [Admission control](/docs/reference/access-authn-authz/admission-controllers/) is a key part of Kubernetes security, alongside authentication and authorization. Webhook admission controllers are extensively used to help improve the security of Kubernetes clusters in a variety of ways including restricting the privileges of workloads and ensuring that images deployed to the cluster meet organization’s security requirements.
 
 However, as with any additional component added to a cluster, security risks can present themselves. A security risk example is if the deployment and management of the admission controller are not handled correctly. To help admission controller users and designers manage these risks appropriately, the [security documentation](https://github.com/kubernetes/community/tree/master/sig-security#security-docs) subgroup of SIG Security has spent some time developing a [threat model for admission controllers](https://github.com/kubernetes/sig-security/tree/main/sig-security-docs/papers/admission-control). This threat model looks at likely risks which may arise from the incorrect use of admission controllers, which could allow security policies to be bypassed, or even allow an attacker to get unauthorised access to the cluster.

diff --git a/content/en/blog/_posts/2022-02-07-sig-multicluster-spotlight/index.md b/content/en/blog/_posts/2022-02-07-sig-multicluster-spotlight/index.md
@@ -4,10 +4,11 @@ title: "Spotlight on SIG Multicluster"
 date: 2022-02-07
 slug: sig-multicluster-spotlight-2022
 canonicalUrl: https://www.kubernetes.dev/blog/2022/02/04/sig-multicluster-spotlight-2022/
+author: >
+   Dewan Ahmed (Aiven),
+   Chris Short (AWS)
 ---
 
-**Authors:** Dewan Ahmed (Aiven) and Chris Short (AWS)
-
 ## Introduction
 
 [SIG Multicluster](https://github.com/kubernetes/community/tree/master/sig-multicluster) is the SIG focused on how Kubernetes concepts are expanded and used beyond the cluster boundary. Historically, Kubernetes resources only interacted within that boundary - KRU or Kubernetes Resource Universe (not an actual Kubernetes concept). Kubernetes clusters, even now, don't really know anything about themselves or, about other clusters. Absence of cluster identifiers is a case in point. With the growing adoption of multicloud and multicluster deployments, the work SIG Multicluster doing is gaining a lot of attention. In this blog, [Jeremy Olmsted-Thompson, Google](https://twitter.com/jeremyot) and [Chris Short, AWS](https://twitter.com/ChrisShort) discuss the interesting problems SIG Multicluster is solving and how you can get involved. Their initials **JOT** and **CS** will be used for brevity.

diff --git a/content/en/blog/_posts/2022-02-16-sig-node-ci-subproject-celebrates/index.md b/content/en/blog/_posts/2022-02-16-sig-node-ci-subproject-celebrates/index.md
@@ -4,10 +4,11 @@ title: 'SIG Node CI Subproject Celebrates Two Years of Test Improvements'
 date: 2022-02-16
 slug: sig-node-ci-subproject-celebrates
 canonicalUrl: https://www.kubernetes.dev/blog/2022/02/16/sig-node-ci-subproject-celebrates-two-years-of-test-improvements/
+author: >
+   Sergey Kanzhelev (Google),
+   Elana Hashman (Red Hat)
 ---
 
-**Authors:** Sergey Kanzhelev (Google), Elana Hashman (Red Hat)
-
 Ensuring the reliability of SIG Node upstream code is a continuous effort
 that takes a lot of behind-the-scenes effort from many contributors.
 There are frequent releases of Kubernetes, base operating systems,

diff --git a/content/en/blog/_posts/2022-03-31-ready-for-dockershim-removal.md b/content/en/blog/_posts/2022-03-31-ready-for-dockershim-removal.md
@@ -3,11 +3,10 @@ layout: blog
 title: "Is Your Cluster Ready for v1.24?"
 date: 2022-03-31
 slug: ready-for-dockershim-removal
+author: >
+   Kat Cosgrove
 ---
 
-**Author:** Kat Cosgrove
-
-
 Way back in December of 2020, Kubernetes announced the [deprecation of Dockershim](/blog/2020/12/02/dont-panic-kubernetes-and-docker/). In Kubernetes, dockershim is a software shim that allows you to use the entire Docker engine as your container runtime within Kubernetes. In the upcoming v1.24 release, we are removing Dockershim - the delay between deprecation and removal in line with the [project’s policy](https://kubernetes.io/docs/reference/using-api/deprecation-policy/) of supporting features for at least one year after deprecation. If you are a cluster operator, this guide includes the practical realities of what you need to know going into this release. Also, what do you need to do to ensure your cluster doesn’t fall over!
 
 ## First, does this even affect you?

diff --git a/content/en/blog/_posts/2022-04-07-Kubernetes-1-24-removals-and-deprecations.md b/content/en/blog/_posts/2022-04-07-Kubernetes-1-24-removals-and-deprecations.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Kubernetes Removals and Deprecations In 1.24"
 date: 2022-04-07
 slug: upcoming-changes-in-kubernetes-1-24
+author: >
+   Mickey Boxell (Oracle)
 ---
 
-**Author**: Mickey Boxell (Oracle)
-
 As Kubernetes evolves, features and APIs are regularly revisited and removed. New features may offer
 an alternative or improved approach to solving existing problems, motivating the team to remove the
 old approach. 

diff --git a/...en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX/index.md b/...en/blog/_posts/2022-04-28-Increasing-the-security-bar-in-Ingress-NGINX/index.md
@@ -3,10 +3,11 @@ layout: blog
 title: 'Increasing the security bar in Ingress-NGINX v1.2.0'
 date: 2022-04-28
 slug: ingress-nginx-1-2-0
+author: >
+   Ricardo Katz (VMware),
+   James Strong (Chainguard)
 ---
 
-**Authors:** Ricardo Katz (VMware), James Strong (Chainguard)
-
 The [Ingress](/docs/concepts/services-networking/ingress/) may be one of the most targeted components
 of Kubernetes. An Ingress typically defines an HTTP reverse proxy, exposed to the Internet, containing
 multiple websites, and with some privileged access to Kubernetes API (such as to read Secrets relating to

diff --git a/content/en/blog/_posts/2022-04-29-kubernetes-1.23-release-interview.md b/content/en/blog/_posts/2022-04-29-kubernetes-1.23-release-interview.md
@@ -2,10 +2,10 @@
 layout: blog
 title: "Frontiers, fsGroups and frogs: the Kubernetes 1.23 release interview"
 date: 2022-04-29
+author: >
+   Craig Box (Google)
 ---
 
-**Author**: Craig Box (Google)
-
 One of the highlights of hosting the weekly [Kubernetes Podcast from Google](https://kubernetespodcast.com/) is talking to the release managers for each new Kubernetes version. The release team is constantly refreshing. Many working their way from small documentation fixes, step up to shadow roles, and then eventually lead a release.
 
 As we prepare for the 1.24 release next week, [in accordance with long-standing tradition](https://www.google.com/search?q=%22release+interview%22+site%3Akubernetes.io%2Fblog), I'm pleased to bring you a look back at the story of 1.23. The release was led by [Rey Lejano](https://twitter.com/reylejano), a Field Engineer at SUSE. [I spoke to Rey](https://kubernetespodcast.com/episode/167-kubernetes-1.23/) in December, as he was awaiting the birth of his first child.

diff --git a/content/en/blog/_posts/2022-05-03-dockershim-historical-context.md b/content/en/blog/_posts/2022-05-03-dockershim-historical-context.md
@@ -3,11 +3,10 @@ layout: blog
 title: "Dockershim: The Historical Context"
 date: 2022-05-03
 slug: dockershim-historical-context
+author: >
+  Kat Cosgrove
 ---
 
-**Author:** Kat Cosgrove
-
-
 Dockershim has been removed as of Kubernetes v1.24, and this is a positive move for the project. However, context is important for fully understanding something, be it socially or in software development, and this deserves a more in-depth review. Alongside the dockershim removal in Kubernetes v1.24, we’ve seen some confusion (sometimes at a panic level) and dissatisfaction with this decision in the community, largely due to a lack of context around this removal. The decision to deprecate and eventually remove dockershim from Kubernetes was not made quickly or lightly. Still, it’s been in the works for so long that many of today’s users are newer than that decision, and certainly newer than the choices that led to the dockershim being necessary in the first place.
 
 So what is the dockershim, and why is it going away?

diff --git a/content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md b/content/en/blog/_posts/2022-05-03-kubernetes-release-1.24.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Kubernetes 1.24: Stargazer"
 date: 2022-05-03
 slug: kubernetes-1-24-release-announcement
+author: >
+  [Kubernetes 1.24 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.24/release-team.md)
 ---
 
-**Authors**: [Kubernetes 1.24 Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.24/release-team.md)
-
 We are excited to announce the release of Kubernetes 1.24, the first release of 2022!
 
 This release consists of 46 enhancements: fourteen enhancements have graduated to stable, 

diff --git a/content/en/blog/_posts/2022-05-05-volume-expansion-ga.md b/content/en/blog/_posts/2022-05-05-volume-expansion-ga.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Kubernetes 1.24: Volume Expansion Now A Stable Feature"
 date: 2022-05-05
 slug: volume-expansion-ga
+author: >
+  Hemant Kumar (Red Hat)
 ---
 
-**Author:** Hemant Kumar (Red Hat)
-
 Volume expansion was introduced as a alpha feature in Kubernetes 1.8 and it went beta in 1.11 and with Kubernetes 1.24 we are excited to announce general availability(GA)
 of volume expansion.
 

diff --git a/content/en/blog/_posts/2022-05-06-storage-capacity-GA/index.md b/content/en/blog/_posts/2022-05-06-storage-capacity-GA/index.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Kubernetes 1.24: Storage Capacity Tracking Now Generally Available"
 date: 2022-05-06
 slug: storage-capacity-ga
+author: >
+   Patrick Ohly (Intel)
 ---
 
- **Authors:** Patrick Ohly (Intel)
-
 The v1.24 release of Kubernetes brings [storage capacity](/docs/concepts/storage/storage-capacity/)
 tracking as a generally available feature.
 

diff --git a/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md b/content/en/blog/_posts/2022-05-13-grpc-probes-in-beta.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Kubernetes 1.24: gRPC container probes in beta"
 date: 2022-05-13
 slug: grpc-probes-now-in-beta
+author: >
+  Sergey Kanzhelev (Google)
 ---
 
-**Author**: Sergey Kanzhelev (Google)
-
 _Update: Since this article was posted, the feature was graduated to GA in v1.27 and doesn't require any feature gates to be enabled.
 
 With Kubernetes 1.24 the gRPC probes functionality entered beta and is available by default.

diff --git a/content/en/blog/_posts/2022-05-16-volume-populators-beta.md b/content/en/blog/_posts/2022-05-16-volume-populators-beta.md
@@ -3,11 +3,10 @@ layout: blog
 title: "Kubernetes 1.24: Volume Populators Graduate to Beta"
 date: 2022-05-16
 slug: volume-populators-beta
+author: >
+  Ben Swartzlander (NetApp)
 ---
 
-**Author:**
-Ben Swartzlander (NetApp)
-
 The volume populators feature is now two releases old and entering beta! The `AnyVolumeDataSource` feature
 gate defaults to enabled in Kubernetes v1.24, which means that users can specify any custom resource
 as the data source of a PVC.

diff --git a/content/en/blog/_posts/2022-05-18-prevent-unauthorised-volume-mode-conversion.md b/content/en/blog/_posts/2022-05-18-prevent-unauthorised-volume-mode-conversion.md
@@ -3,10 +3,10 @@ layout: blog
 title: 'Kubernetes 1.24: Prevent unauthorised volume mode conversion'
 date: 2022-05-18
 slug: prevent-unauthorised-volume-mode-conversion-alpha
+author: >
+  Raunak Pradip Shah (Mirantis)
 ---
 
-**Author:** Raunak Pradip Shah (Mirantis)
-
 Kubernetes v1.24 introduces a new alpha-level feature that prevents unauthorised users 
 from modifying the volume mode of a [`PersistentVolumeClaim`](/docs/concepts/storage/persistent-volumes/) created from an 
 existing [`VolumeSnapshot`](/docs/concepts/storage/volume-snapshots/) in the Kubernetes cluster.  

diff --git a/content/en/blog/_posts/2022-05-20-non-graceful-node-shutdown.md b/content/en/blog/_posts/2022-05-20-non-graceful-node-shutdown.md
@@ -3,10 +3,11 @@ layout: blog
 title: "Kubernetes 1.24: Introducing Non-Graceful Node Shutdown Alpha"
 date: 2022-05-20
 slug: kubernetes-1-24-non-graceful-node-shutdown-alpha
+author: >
+  Xing Yang (VMware),
+  Yassine Tijani (VMware)
 ---
 
-**Authors** Xing Yang and Yassine Tijani (VMware)
-
 Kubernetes v1.24 introduces alpha support for [Non-Graceful Node Shutdown](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2268-non-graceful-shutdown). This feature allows stateful workloads to failover to a different node after the original node is shutdown or in a non-recoverable state such as hardware failure or broken OS.
 
 ## How is this different from Graceful Node Shutdown

diff --git a/content/en/blog/_posts/2022-05-23-service-ip-dynamic-and-static-allocation.md b/content/en/blog/_posts/2022-05-23-service-ip-dynamic-and-static-allocation.md
@@ -3,11 +3,10 @@ layout: blog
 title: "Kubernetes 1.24: Avoid Collisions Assigning IP Addresses to Services"
 date: 2022-05-23
 slug: service-ip-dynamic-and-static-allocation
+author: >
+  Antonio Ojea (Red Hat)
 ---
 
-**Author:** Antonio Ojea (Red Hat)
-
-
 In Kubernetes, [Services](/docs/concepts/services-networking/service/) are an abstract way to expose
 an application running on a set of Pods. Services
 can have a cluster-scoped virtual IP address (using a Service of `type: ClusterIP`).

diff --git a/content/en/blog/_posts/2022-05-25-contextual-logging/index.md b/content/en/blog/_posts/2022-05-25-contextual-logging/index.md
@@ -4,10 +4,10 @@ title: "Contextual Logging in Kubernetes 1.24"
 date: 2022-05-25
 slug: contextual-logging
 canonicalUrl: https://kubernetes.dev/blog/2022/05/25/contextual-logging/
+author: >
+   Patrick Ohly (Intel)
 ---
 
- **Authors:** Patrick Ohly (Intel)
-
 The [Structured Logging Working
 Group](https://github.com/kubernetes/community/blob/master/wg-structured-logging/README.md)
 has added new capabilities to the logging infrastructure in Kubernetes

diff --git a/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md b/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md
@@ -3,10 +3,10 @@ layout: blog
 title: 'Kubernetes 1.24: Maximum Unavailable Replicas for StatefulSet'
 date: 2022-05-27
 slug: maxunavailable-for-statefulset
+author: >
+  Mayank Kumar (Salesforce)
 ---
 
-**Author:** Mayank Kumar (Salesforce)
-
 Kubernetes [StatefulSets](/docs/concepts/workloads/controllers/statefulset/), since their introduction in 
 1.5 and becoming stable in 1.9, have been widely used to run stateful applications. They provide stable pod identity, persistent
 per pod storage and ordered graceful deployment, scaling and rolling updates. You can think of StatefulSet as the atomic building

diff --git a/content/en/blog/_posts/2022-06-01-annual-report-2021.md b/content/en/blog/_posts/2022-06-01-annual-report-2021.md
@@ -3,10 +3,10 @@ layout: blog
 title: "Annual Report Summary 2021"
 date: 2022-06-01
 slug: annual-report-summary-2021
+author: >
+  Paris Pittman (Steering Committee)
 ---
 
-**Author:** Paris Pittman (Steering Committee)
-
 Last year, we published our first [Annual Report Summary](/blog/2021/06/28/announcing-kubernetes-community-group-annual-reports/) for 2020 and it's already time for our second edition!
 
 [2021 Annual Report Summary](https://www.cncf.io/reports/kubernetes-annual-report-2021/)

diff --git a/content/en/blog/_posts/2022-07-13-gateway-api-in-beta.md b/content/en/blog/_posts/2022-07-13-gateway-api-in-beta.md
@@ -4,10 +4,13 @@ title: Kubernetes Gateway API Graduates to Beta
 date: 2022-07-13
 slug: gateway-api-graduates-to-beta
 canonicalUrl: https://gateway-api.sigs.k8s.io/blog/2022/graduating-to-beta/
+author: >
+  Shane Utt (Kong),
+  Rob Scott (Google),
+  Nick Young (VMware),
+  Jeff Apple (HashiCorp)
 ---
 
-**Authors:** Shane Utt (Kong), Rob Scott (Google), Nick Young (VMware), Jeff Apple (HashiCorp)
-
 We are excited to announce the v0.5.0 release of Gateway API. For the first
 time, several of our most important Gateway API resources are graduating to
 beta. Additionally, we are starting a new initiative to explore how Gateway API

diff --git a/content/en/blog/_posts/2022-08-02-sig-docs-spotlight/index.md b/content/en/blog/_posts/2022-08-02-sig-docs-spotlight/index.md
@@ -4,10 +4,10 @@ title: "Spotlight on SIG Docs"
 date: 2022-08-02
 slug: sig-docs-spotlight-2022
 canonicalUrl: https://kubernetes.dev/blog/2022/08/02/sig-docs-spotlight-2022/
+author: >
+   Purneswar Prasad
 ---
 
-**Author:** Purneswar Prasad
-
 ## Introduction
 
 The official documentation is the go-to source for any open source project. For Kubernetes, 

diff --git a/content/en/blog/_posts/2022-08-03-kms-v2-alpha.md b/content/en/blog/_posts/2022-08-03-kms-v2-alpha.md
@@ -3,10 +3,13 @@ layout: blog
 title: "Kubernetes 1.25: KMS V2 Improvements"
 date: 2022-09-09
 slug: kms-v2-improvements
+author: >
+  Anish Ramasekar,
+  Rita Zhang,
+  Mo Khan,
+  Xander Grzywinski (Microsoft)
 ---
 
-**Authors:** Anish Ramasekar, Rita Zhang, Mo Khan, and Xander Grzywinski (Microsoft)
-
 With Kubernetes v1.25, SIG Auth is introducing a new `v2alpha1` version of the Key Management Service (KMS) API. There are a lot of improvements in the works, and we're excited to be able to start down the path of a new and improved KMS!
 
 ## What is KMS?

diff --git a/content/en/blog/_posts/2022-08-04-kubernetes-1.25-deprecations-and-removals.md b/content/en/blog/_posts/2022-08-04-kubernetes-1.25-deprecations-and-removals.md
@@ -3,10 +3,12 @@ layout: blog
 title: "Kubernetes Removals and Major Changes In 1.25"
 date: 2022-08-04
 slug: upcoming-changes-in-kubernetes-1-25
+author: >
+  Kat Cosgrove,
+  Frederico Muñoz,
+  Debabrata Panigrahi
 ---
 
-**Authors**: Kat Cosgrove, Frederico Muñoz, Debabrata Panigrahi
-
 As Kubernetes grows and matures, features may be deprecated, removed, or replaced with improvements for the health of the project. Kubernetes v1.25 includes several major changes and one major removal.
 
 ## The Kubernetes API Removal and Deprecation process

diff --git a/content/en/blog/_posts/2022-08-11-enhancing-kubernetes-one-kep-at-a-time/index.md b/content/en/blog/_posts/2022-08-11-enhancing-kubernetes-one-kep-at-a-time/index.md
@@ -4,10 +4,10 @@ title: "Enhancing Kubernetes one KEP at a Time"
 date: 2022-08-11
 slug: enhancing-kubernetes-one-kep-at-a-time
 canonicalUrl: https://www.k8s.dev/blog/2022/08/11/enhancing-kubernetes-one-kep-at-a-time/
+author: >
+  Ryler Hockenbury (Mastercard)
 ---
 
-**Author:** Ryler Hockenbury (Mastercard)
-
 Did you know that Kubernetes v1.24 has [46 enhancements](https://kubernetes.io/blog/2022/05/03/kubernetes-1-24-release-announcement/)? That's a lot of new functionality packed into a 4-month release cycle. The Kubernetes release team coordinates the logistics of the release, from remediating test flakes to publishing updated docs. It's a ton of work, but they always deliver.
 
 The release team comprises around 30 people across six subteams - Bug Triage, CI Signal, Enhancements, Release Notes, Communications, and Docs.  Each of these subteams manages a component of the release. This post will focus on the role of the enhancements subteam and how you can get involved.

diff --git a/content/en/blog/_posts/2022-08-16-PSP-historical-context/index.md b/content/en/blog/_posts/2022-08-16-PSP-historical-context/index.md
@@ -4,10 +4,10 @@ title: "PodSecurityPolicy: The Historical Context"
 date: 2022-08-23T15:00:00-0800
 slug: podsecuritypolicy-the-historical-context
 evergreen: true
+author: >
+  Mahé Tardy (Quarkslab)
 ---
 
-**Author:** Mahé Tardy (Quarkslab)
-
 The PodSecurityPolicy (PSP) admission controller has been removed, as of
 Kubernetes v1.25. Its deprecation was announced and detailed in the blog post
 [PodSecurityPolicy Deprecation: Past, Present, and Future](/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/),

diff --git a/content/en/blog/_posts/2022-08-18-kubernetes-1.24-release-interview.md b/content/en/blog/_posts/2022-08-18-kubernetes-1.24-release-interview.md
@@ -2,10 +2,10 @@
 layout: blog
 title: "Stargazing, solutions and staycations: the Kubernetes 1.24 release interview"
 date: 2022-08-18
+author: >
+  Craig Box (Google)
 ---
 
-**Author**: Craig Box (Google)
-
 The Kubernetes project has participants from all around the globe. Some are friends, some are colleagues, and some are strangers. The one thing that unifies them, no matter their differences, are that they all have an interesting story. It is my pleasure to be the documentarian for the stories of the Kubernetes community in the weekly [Kubernetes Podcast from Google](https://kubernetespodcast.com/). With every new Kubernetes release comes an interview with the release team lead, telling the story of that release, but also their own personal story.
 
 With 1.25 around the corner, [the tradition continues](https://www.google.com/search?q=%22release+interview%22+site%3Akubernetes.io%2Fblog) with a look back at the story of 1.24. That release was led by [James Laverack](https://twitter.com/jameslaverack) of Jetstack. [James was on the podcast](https://kubernetespodcast.com/episode/178-kubernetes-1.24/) in May, and while you can read his story below, if you can, please do listen to it in his own voice.

diff --git a/content/en/blog/_posts/2022-08-22-sig-storage-spotlight.md b/content/en/blog/_posts/2022-08-22-sig-storage-spotlight.md
@@ -4,10 +4,10 @@ title: "Spotlight on SIG Storage"
 slug: sig-storage-spotlight
 date: 2022-08-22
 canonicalUrl: https://www.kubernetes.dev/blog/2022/08/22/sig-storage-spotlight-2022/
+author: >
+  Frederico Muñoz (SAS)
 ---
 
-**Author**: Frederico Muñoz (SAS)
-
 Since the very beginning of Kubernetes, the topic of persistent data and how to address the requirement of stateful applications has been an important topic. Support for stateless deployments was natural, present from the start, and garnered attention, becoming very well-known. Work on better support for stateful applications was also present from early on, with each release increasing the scope of what could be run on Kubernetes.
 
 Message queues, databases, clustered filesystems: these are some examples of the solutions that have different storage requirements and that are, today, increasingly deployed in Kubernetes. Dealing with ephemeral and persistent storage, local or remote, file or block, from many different vendors, while considering how to provide the needed resiliency and data consistency that users expect, all of this is under SIG Storage's umbrella.