Application of code include widget, hack curl calls for three file downloads, saas code/pre fixes, comment-out of version drop-down

2016-03-01 19:43:10 -08:00
parent df6a183084
commit 50704476d6
17 changed files with 102 additions and 378 deletions
@@ -87,21 +87,7 @@ In order for the Ingress resource to work, the cluster must have an Ingress cont

 There are existing Kubernetes concepts that allow you to expose a single service (see [alternatives](#alternatives)), however you can do so through an Ingress as well, by specifying a *default backend* with no rules.

-<!-- BEGIN MUNGE: EXAMPLE ingress.yaml -->
-
-```yaml
-apiVersion: extensions/v1beta1
-kind: Ingress
-metadata:
-  name: test-ingress
-spec:
-  backend:
-    serviceName: testsvc
-    servicePort: 80
-```
-
-[Download example](/docs/user-guide/ingress.yaml)
-<!-- END MUNGE: EXAMPLE ingress.yaml -->
+{% include code.html language="yaml" file="ingress.yaml" ghlink="/docs/user-guide/ingress.yaml" %}

 If you create it using `kubectl -f` you should see: