From 147e8616f4721ad7f809e480f15e37320a30bcd2 Mon Sep 17 00:00:00 2001
From: Rob Scott <robertjscott@google.com>
Date: Thu, 9 Apr 2020 11:54:21 -0700
Subject: [PATCH] Adding quotes to examples in Ingress blog post

---
 ...s-to-the-Ingress-API-in-Kubernetes-1.18.md | 34 +++++++++----------
 1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/content/en/blog/_posts/2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md b/content/en/blog/_posts/2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md
index 0d78e3206b..6fdb291c5b 100644
--- a/content/en/blog/_posts/2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md
+++ b/content/en/blog/_posts/2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md
@@ -24,17 +24,17 @@ The new concept of a path type allows you to specify how a path should be matche
 The Ingress resource was designed with simplicity in mind, providing a simple set of fields that would be applicable in all use cases. Over time, as use cases evolved, implementations began to rely on a long list of custom annotations for further configuration. The new `IngressClass` resource provides a way to replace some of those annotations.
 
 Each `IngressClass` specifies which controller should implement Ingresses of the class and can reference a custom resource with additional parameters. 
-```
-apiVersion: networking.k8s.io/v1beta1
-kind: IngressClass
+```yaml
+apiVersion: "networking.k8s.io/v1beta1"
+kind: "IngressClass"
 metadata:
-  name: external-lb
+  name: "external-lb"
 spec:
-  controller: example.com/ingress-controller
+  controller: "example.com/ingress-controller"
   parameters:
-    apiGroup: k8s.example.com/v1alpha
-    kind: IngressParameters
-    name: external-lb
+    apiGroup: "k8s.example.com/v1alpha"
+    kind: "IngressParameters"
+    name: "external-lb"
 ```
 
 ### Specifying the Class of an Ingress
@@ -60,21 +60,21 @@ Many Ingress providers have supported wildcard hostname matching like `*.foo.com
 ### Putting it All Together
 These new Ingress features allow for much more configurability. Here’s an example of an Ingress that makes use of pathType, `ingressClassName`, and a hostname wildcard:
 
-```
-apiVersion: networking.k8s.io/v1beta1
-kind: Ingress
+```yaml
+apiVersion: "networking.k8s.io/v1beta1"
+kind: "Ingress"
 metadata:
-  name: example-ingress
+  name: "example-ingress"
 spec:
-  ingressClassName: external-lb
+  ingressClassName: "external-lb"
   rules:
-  - host: *.example.com
+  - host: "*.example.com"
     http:
       paths:
-      - path: /example
-        pathType: Prefix
+      - path: "/example"
+        pathType: "Prefix"
         backend:
-          serviceName: example-service
+          serviceName: "example-service"
           servicePort: 80
 ```