From 360a842673f14366a89328ec322efb8e3243dc31 Mon Sep 17 00:00:00 2001
From: Kenichi Omichi <ken-oomichi@wx.jp.nec.com>
Date: Mon, 6 May 2019 17:43:41 -0700
Subject: [PATCH] Fix orders of yaml of services-networking/ingress (#14192)

The order of kind and metadata were inconsistent, and that made the
doc unreadable.
This fixes the orders in consistent way in ingress.md
---
 content/en/docs/concepts/services-networking/ingress.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
index 22b3a4e4d7..7ddd637ec8 100644
--- a/content/en/docs/concepts/services-networking/ingress.md
+++ b/content/en/docs/concepts/services-networking/ingress.md
@@ -305,13 +305,13 @@ and private key to use for TLS, e.g.:
 
 ```yaml
 apiVersion: v1
-data:
-  tls.crt: base64 encoded cert
-  tls.key: base64 encoded key
 kind: Secret
 metadata:
   name: testsecret-tls
   namespace: default
+data:
+  tls.crt: base64 encoded cert
+  tls.key: base64 encoded key
 type: kubernetes.io/tls
 ```