Merge pull request #46234 from dipesh-rawat/blog-post-2019-add-author

Update 2019 blog content files to move author details in front-matter

Author: k8s-ci-robot

content/en/blog/_posts/2019-01-14-apiserver-dry-run-and-kubectl-diff.md

@@ -2,10 +2,10 @@
 layout: blog
 title: 'APIServer dry-run and kubectl diff'
 date: 2019-01-14
+author: >
+  Antoine Pelisse (Google Cloud) 
 ---
 
-**Author**: Antoine Pelisse (Google Cloud, @apelisse)
-
 Declarative configuration management, also known as configuration-as-code, is
 one of the key strengths of Kubernetes. It allows users to commit the desired state of
 the cluster, and to keep track of the different versions, improve auditing and

content/en/blog/_posts/2019-01-15-container-storage-interface-ga.md

@@ -2,13 +2,13 @@
 title: Container Storage Interface (CSI) for Kubernetes GA
 date: 2019-01-15
 slug: container-storage-interface-ga
+author: >
+  Saad Ali (Google)
 ---
 
 ![Kubernetes Logo](/images/blog-logging/2018-04-10-container-storage-interface-beta/csi-kubernetes.png)
 ![CSI Logo](/images/blog-logging/2018-04-10-container-storage-interface-beta/csi-logo.png)
 
-**Author:** Saad Ali, Senior Software Engineer, Google
-
 The Kubernetes implementation of the [Container Storage Interface](https://github.com/container-storage-interface/spec/blob/master/spec.md) (CSI) has been promoted to GA in the Kubernetes v1.13 release. Support for CSI was [introduced as alpha](http://blog.kubernetes.io/2018/01/introducing-container-storage-interface.html) in Kubernetes v1.9 release, and [promoted to beta](https://kubernetes.io/blog/2018/04/10/container-storage-interface-beta/) in the Kubernetes v1.10 release.
 
 The GA milestone indicates that Kubernetes users may depend on the feature and its API without fear of backwards incompatible changes in future causing regressions. GA features are protected by the [Kubernetes deprecation policy](/docs/reference/using-api/deprecation-policy/).

content/en/blog/_posts/2019-01-17-update-volume-snapshot-alpha.md

@@ -1,10 +1,12 @@
 ---
 title: Update on Volume Snapshot Alpha for Kubernetes
 date: 2019-01-17
+author: >
+  DJing Xu (Google),
+  Xing Yang (Huawei),
+  Saad Ali (Google)
 ---
 
-**Authors:** Jing Xu (Google), Xing Yang (Huawei), Saad Ali (Google)
-
 Volume snapshotting support was introduced in Kubernetes v1.12 as an alpha feature. In Kubernetes v1.13, it remains an alpha feature, but a few enhancements were added and some breaking changes were made. This post summarizes the changes.
 
 ## Breaking Changes

content/en/blog/_posts/2019-02-06-poseidon-firmament-scheduler-announcement.md

@@ -1,10 +1,11 @@
 ---
 title: Poseidon-Firmament Scheduler – Flow Network Graph Based Scheduler
 date: 2019-02-06
+author: >
+  Deepak Vij (Huawei),
+  Shivram Shrivastava (Huawei)  
 ---
 
-**Authors:** Deepak Vij (Huawei), Shivram Shrivastava (Huawei)  
-
 ## Introduction  
 
 Cluster Management systems such as Mesos, Google Borg, Kubernetes etc. in a cloud scale datacenter environment (also termed as ***Datacenter-as-a-Computer*** or ***Warehouse-Scale Computing - WSC***) typically manage application workloads by performing tasks such as tracking machine live-ness, starting, monitoring, terminating workloads and more importantly using a **Cluster Scheduler** to decide on workload placements.

content/en/blog/_posts/2019-02-11-runc-CVE-2019-5736.md

@@ -2,10 +2,10 @@
 title: Runc and CVE-2019-5736
 date: 2019-02-11
 evergreen: false # mentions PodSecurityPolicy
+author: >
+  Kubernetes Product Security Committee
 ---
 
-Authors: Kubernetes Product Security Committee
-
 This morning [a container escape vulnerability in runc was announced](https://www.openwall.com/lists/oss-security/2019/02/11/2). We wanted to provide some guidance to Kubernetes users to ensure everyone is safe and secure.
 
 ## What is runc?

content/en/blog/_posts/2019-02-12-building-a-kubernetes-edge-control-plane-for-envoy-v2.md

@@ -2,15 +2,13 @@
 title: Building a Kubernetes Edge (Ingress) Control Plane for Envoy v2
 date: 2019-02-12
 slug: building-a-kubernetes-edge-control-plane-for-envoy-v2
+author: >
+  Daniel Bryant (Datawire),
+  Flynn (Datawire),
+  Richard Li (Datawire) 
 ---
 
 
-**Author:**
-Daniel Bryant, Product Architect, Datawire;
-Flynn, Ambassador Lead Developer, Datawire;
-Richard Li, CEO and Co-founder, Datawire
-
-
 Kubernetes has become the de facto runtime for container-based microservice applications, but this orchestration framework alone does not provide all of the infrastructure necessary for running a distributed system. Microservices typically communicate through Layer 7 protocols such as HTTP, gRPC, or WebSockets, and therefore having the ability to make routing decisions, manipulate protocol metadata, and observe at this layer is vital. However, traditional load balancers and edge proxies have predominantly focused on L3/4 traffic. This is where the [Envoy Proxy](https://www.envoyproxy.io/) comes into play.
 
 Envoy proxy was designed as a [universal data plane](https://blog.envoyproxy.io/the-universal-data-plane-api-d15cec7a) from the ground-up by the Lyft Engineering team for today's distributed, L7-centric world, with broad support for L7 protocols, a real-time API for managing its configuration, first-class observability, and high performance within a small memory footprint. However, Envoy's vast feature set and flexibility of operation also makes its configuration highly complicated -- this is evident from looking at its rich but verbose [control plane](https://blog.envoyproxy.io/service-mesh-data-plane-vs-control-plane-2774e720f7fc) syntax.

content/en/blog/_posts/2019-02-28-automate-operations-on-your-cluster-with-operatorhub.md

@@ -1,11 +1,10 @@
 ---
 title: Automate Operations on your Cluster with OperatorHub.io
 date: 2019-02-28
+author: >
+  Diane Mueller (Red Hat)
 ---
 
-**Author:**
-Diane Mueller, Director of Community Development, Cloud Platforms, Red Hat
-
 One of the important challenges facing developers and Kubernetes administrators has been a lack of ability to quickly find common services that are operationally ready for Kubernetes. Typically, the presence of an Operator for a specific service - a pattern that was introduced in 2016 and has gained momentum - is a good signal for the operational readiness of the service on Kubernetes. However, there has to date not existed a registry of Operators to simplify the discovery of such services.   
 
 To help address this challenge, today Red Hat is launching OperatorHub.io in collaboration with AWS, Google Cloud and Microsoft. OperatorHub.io enables developers and Kubernetes administrators to find and install curated Operator-backed services with a base level of documentation, active maintainership by communities or vendors, basic testing, and packaging for optimized life-cycle management on Kubernetes.  

content/en/blog/_posts/2019-03-07-raw-block-volume-support-to-beta.md

@@ -1,11 +1,11 @@
 ---
 title: Raw Block Volume support to Beta
 date: 2019-03-07
+author: >
+  Ben Swartzlander (NetApp),
+  Saad Ali (Google) 
 ---
 
-**Authors:**
-Ben Swartzlander (NetApp), Saad Ali (Google)
-
 Kubernetes v1.13 moves raw block volume support to beta. This feature allows persistent volumes to be exposed inside containers as a block device instead of as a mounted file system.
 
 ## What are block devices?

content/en/blog/_posts/2019-03-15-Kubernetes-setup-using-Ansible-and-Vagrant.md

@@ -2,10 +2,10 @@
 layout: blog
 title: Kubernetes Setup Using Ansible and Vagrant
 date: 2019-03-15
+author: >
+  Naresh L J (Infosys) 
 ---
 
-**Author:** Naresh L J (Infosys)
-
 ## Objective
 This blog post describes the steps required to setup a multi node Kubernetes cluster for development purposes. This setup provides a production-like cluster that can be setup on your local machine. 
 

content/en/blog/_posts/2019-03-19-kubeedge-k8s-based-edge-intro.md

@@ -2,10 +2,11 @@
 title: KubeEdge, a Kubernetes Native Edge Computing Framework
 date: 2019-03-19
 slug: kubeedge-k8s-based-edge-intro
+author: >
+  Sanil Kumar D (Huawei),
+  Jun Du(Huawei)
 ---
 
-**Author:** Sanil Kumar D (Huawei), Jun Du(Huawei)
-
 ## KubeEdge becomes the first Kubernetes Native Edge Computing Platform with both Edge and Cloud components open sourced!
 
 Open source edge computing is going through its most dynamic phase of development in the industry. So many open source platforms, so many consolidations and so many initiatives for standardization! This shows the strong drive to build better platforms to bring cloud computing to the edges to meet ever increasing demand. [KubeEdge](https://github.com/kubeedge/kubeedge), which was announced last year, now brings great news for cloud native computing! It provides a complete edge computing solution based on Kubernetes with separate cloud and edge core modules. Currently, both the cloud and edge modules are open sourced.