<!--
  ~ Copyright (C) 2015 Original Authors
  ~
  ~ Licensed under the Apache License, Version 2.0 (the "License");
  ~ you may not use this file except in compliance with the License.
  ~ You may obtain a copy of the License at
  ~
  ~         http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~ Unless required by applicable law or agreed to in writing, software
  ~ distributed under the License is distributed on an "AS IS" BASIS,
  ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  ~ See the License for the specific language governing permissions and
  ~ limitations under the License.
  -->

The raw yaml of a Pod API Object.  Any pod fields set with non-empty values via the configuration fields above will generally take precedence
as they are merged with this yaml, though in the case of arrays (like Volumes or Tolerations) the objects in the yaml will be appeneded to the 
existing list.

Fragments of a full Pod API Object yaml representation are allowed, but you must specify enough of the structure to give context
for the object construction.

For example, you can start with:

```
apiVersion: v1
kind: Pod
spec:
....
```

Or you can just specify the `metadata:` and `spec:` sections as needed.


<!--
  ~ Copyright (C) 2015 Original Authors
  ~
  ~ Licensed under the Apache License, Version 2.0 (the "License");
  ~ you may not use this file except in compliance with the License.
  ~ You may obtain a copy of the License at
  ~
  ~         http://www.apache.org/licenses/LICENSE-2.0
  ~
  ~ Unless required by applicable law or agreed to in writing, software
  ~ distributed under the License is distributed on an "AS IS" BASIS,
  ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  ~ See the License for the specific language governing permissions and
  ~ limitations under the License.
  -->

<p>
The raw yaml of a Pod API Object.  Any pod fields set with non-empty values via the configuration fields above will generally take precedence
as they are merged with this yaml, though in the case of arrays (like Volumes or Tolerations) the objects in the yaml will be appeneded to the
existing list.
</p>

<p>
Fragments of a full Pod API Object yaml representation are allowed, but you must specify enough of the structure to give context
for the object construction.
</p>

<p>
For example, you can start with:

<pre>
apiVersion: v1
kind: Pod
spec:
....
</pre>
</p>

<p>
Or you can just specify the <code>metadata:</code> and <code>spec:</code> sections as needed.
</p>

Fix inline help formatting for yaml option
Fix inline help formatting for yaml option
