Update 2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md

Fixed wildcard host match examples.

Author: zerkms

content/en/blog/_posts/2020-04-02-Improvements-to-the-Ingress-API-in-Kubernetes-1.18.md

@@ -51,11 +51,11 @@ IngressClass resource will ensure that new Ingresses without an `ingressClassNam
 ## Support for Hostname Wildcards
 Many Ingress providers have supported wildcard hostname matching like `*.foo.com` matching `app1.foo.com`, but until now the spec assumed an exact FQDN match of the host. Hosts can now be precise matches (for example “`foo.bar.com`”) or a wildcard (for example “`*.foo.com`”). Precise matches require that the http host header matches the Host setting. Wildcard matches require the http host header is equal to the suffix of the wildcard rule.
 
-| Host        | Host header           | Match?  |
-| ------------- |-------------| -----|
-| `*.foo.com`      | `*.foo.com` | Matches based on shared suffix |
-| `*.foo.com`      | `*.foo.com`      |   No match, wildcard only covers a single DNS label |
-| `*.foo.com` | `foo.com`      |    No match, wildcard only covers a single DNS label |
+| Host        | Host header       | Match?                                            |
+| ----------- |-------------------| --------------------------------------------------|
+| `*.foo.com` | `bar.foo.com`     | Matches based on shared suffix                    |
+| `*.foo.com` | `baz.bar.foo.com` | No match, wildcard only covers a single DNS label |
+| `*.foo.com` | `foo.com`         | No match, wildcard only covers a single DNS label |
 
 ### 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:
@@ -84,4 +84,4 @@ Since these features are new in Kubernetes 1.18, each Ingress controller impleme
 ## The Future of Ingress
 The Ingress API is on pace to graduate from beta to a stable API in Kubernetes 1.19. It will continue to provide a simple way to manage inbound network traffic for Kubernetes workloads. This API has intentionally been kept simple and lightweight, but there has been a desire for greater configurability for more advanced use cases. 
 
-Work is currently underway on a new highly configurable set of APIs that will provide an alternative to Ingress in the future. These APIs are being referred to as the new “Service APIs”. They are not intended to replace any existing APIs, but instead provide a more configurable alternative for complex use cases.  For more information, check out the [Service APIs repo on GitHub](http://github.com/kubernetes-sigs/service-apis).
+Work is currently underway on a new highly configurable set of APIs that will provide an alternative to Ingress in the future. These APIs are being referred to as the new “Service APIs”. They are not intended to replace any existing APIs, but instead provide a more configurable alternative for complex use cases.  For more information, check out the [Service APIs repo on GitHub](http://github.com/kubernetes-sigs/service-apis).