removed 182 fix, which was surprisingly controversial

3.component_model.md

@@ -266,16 +266,14 @@ Resources describe compute resources attached to a runtime.
 
 | Attribute | Type | Required | Default Value | Description |
 |-----------|------|----------|---------------|-------------|
-| `cpu` | [`CPU`](#cpu) | N |  | Specifies the attributes of the cpu resource required for the container. |
+| `cpu` | [`CPU`](#cpu) | Y |  | Specifies the attributes of the cpu resource required for the container. |
 | `memory` | [`Memory`](#memory) | N | | Specifies the attributes of the memory resource required for the container. |
-| `gpu` | [`GPU`](#gpu) | N |  | Specifies the attributes of the gpu resources required for the container. |
+| `gpu` | [`GPU`](#gpu) | Y |  | Specifies the attributes of the gpu resources required for the container. |
 | `volumes` | [`[]Volume`](#volume) | N | | Specifies the attributes of the volumes that the container uses. |
 | `extended` | [`[]ExtendedResource`](#extendedresource) | N | | Implementation-specific extended resource requirements |
 
 For any resource that cannot be satisfied by the underlying platform, the platform MUST return an error and cease deployment. A resource is considered a requirement, and failure to meet that requirement means the runtime MUST NOT deploy the application. For example, if an application requests `1P` of memory, and that amount of memory is not available, the application deployment must fail. Likewise, if an application requires `1` gpu, and the runtime does not provide gpus, the application deployment MUST fail.
 
-If resources are not specified, the underlying platform is free to choose a suitable default.
-
 #### CPU
 
 | Attribute | Type | Required | Default Value | Description |