Update 2022 blog to include author in front-matter

Author: dipesh-rawat

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

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.

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.

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,

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?

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. 

content/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

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.

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?

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,