Update k8s deployer properties. (spring-attic#5748)

References: spring-attic#5406

Author: Corneil du Plessis

spring-cloud-dataflow-docs/src/main/asciidoc/configuration-kubernetes.adoc

@@ -124,6 +124,18 @@ These properties are also used when configuring the <<configuration-kubernetes-t
 |The CPU limit, maximum needed value to allocate a pod
 |<none>
 
+|limits.ephemeral-storage
+|The ephemeral-storage limit, maximum needed value to allocate a pod.
+|<none>
+
+|limits.hugepages-2Mi
+|The hugepages-2Mi limit, maximum needed value to allocate a pod.
+|<none>
+
+|limits.hugepages-1Gi
+|The hugepages-1Gi limit, maximum needed value to allocate a pod.
+|<none>
+
 |requests.memory
 |The memory request, guaranteed needed value to allocate a pod.
 |<none>
@@ -132,6 +144,18 @@ These properties are also used when configuring the <<configuration-kubernetes-t
 |The CPU request, guaranteed needed value to allocate a pod.
 |<none>
 
+|requests.ephemeral-storage
+|The ephemeral-storage request, guaranteed needed value to allocate a pod.
+|<none>
+
+|requests.hugepages-2Mi
+|The hugepages-2Mi request, guaranteed needed value to allocate a pod.
+|<none>
+
+|requests.hugepages-1Gi
+|The hugepages-1Gi request, guaranteed needed value to allocate a pod.
+|<none>
+
 |affinity.nodeAffinity
 |The node affinity expressed in YAML format.  e.g. ```{ requiredDuringSchedulingIgnoredDuringExecution: { nodeSelectorTerms: [ { matchExpressions: [ { key: 'kubernetes.io/e2e-az-name', operator: 'In', values: [ 'e2e-az1', 'e2e-az2']}]}]}, preferredDuringSchedulingIgnoredDuringExecution: [ { weight: 1, preference: { matchExpressions: [ { key: 'another-node-label-key', operator: 'In', values: [ 'another-node-label-value' ]}]}}]}```
 |<none>
@@ -830,7 +854,7 @@ Using the `boot` Entry Point Style corresponds to using the `exec` style `ENTRYP
 
 When scheduling an application, You can clean up finished Jobs (either Complete or Failed) automatically by specifying `ttlSecondsAfterFinished` value.
 
-The following example shows how you can individually configure application jobs:
+The following example shows how you can configure for scheduled application jobs:
 
 ====
 [source,options=nowrap]
@@ -839,6 +863,15 @@ deployer.<application>.kubernetes.cron.ttlSecondsAfterFinished=86400
 ----
 ====
 
+The following example shows how you can individually configure application jobs:
+
+====
+[source,options=nowrap]
+----
+deployer.<application>.kubernetes.ttlSecondsAfterFinished=86400
+----
+====
+
 Replace `<application>` with the name of your application and the `ttlSecondsAfterFinished` attribute with the appropriate value for clean up finished Jobs.
 
 You can configure the `ttlSecondsAfterFinished` at the global server level as well.