wip

Author: markxnelson

site/quickstart.md

@@ -180,13 +180,27 @@ d.	Create an Ingress for the domain, in the domain namespace, by using the [samp
 ```
 $ cd kubernetes/samples/charts
 $ helm install ingress-per-domain --name domain1-ingress --values ingress-per-domain/values.yaml
-```
-
-**TODO** fix this 
-
-e.	Confirm that the load balancer noticed the new Ingress and is successfully routing to the domain's server pods:
-```
-$ curl http://${HOSTNAME}:30305/sample-domain1/
+``` 
+
+e.	To confirm that the load balancer noticed the new Ingress and is successfully routing to the domain's server pods
+    you can hit the URL for the "WebLogic Ready App" which will return a HTTP 200 status code as
+    shown in the example below.  If you used the host-based routing ingress sample you will need to 
+    provide the hostname in the `-H` option:
+```
+$ curl -v -H 'host: domain1.org' http://den01smd.us.oracle.com:30305/weblogic/

+* 
About to connect() to den01smd.us.oracle.com port 30305 (#0)

+*   Trying 10.196.1.64...

+* Connected to den01smd.us.oracle.com (10.196.1.64) port 30305 (#0)
+
> GET /weblogic/ HTTP/1.1

+> User-Agent: curl/7.29.0

+> Accept: */*

+> host: domain1.org

+> 
+
< HTTP/1.1 200 OK

+< Content-Length: 0

+< Date: Thu, 20 Dec 2018 14:52:22 GMT
+
< Vary: Accept-Encoding

+< 
* Connection #0 to host den01smd.us.oracle.com left intact

 ```
 **Note**: Depending on where your Kubernetes cluster is running, you may need to open firewall ports or
 update security lists to allow ingress to this port.