Chapter 3. Bug fixes
This section describes bugs fixed in OpenShift sandboxed containers 1.7.
3.1. Performance and scaling
Peer pod fails when its resource request annotations do not match system resources
The values of the io.katacontainers.config.hypervisor.default_vcpus and io.katacontainers.config.hypervisor.default_memory annotations follow the semantics for QEMU, which has the following limitations for peer pods:
If you set
io.katacontainers.config.hypervisor.default_memoryto less than256, the following error is displayed:Failed to create pod sandbox: rpc error: code = Unknown desc = CreateContainer failed: Memory specified in annotation io.katacontainers.config.hypervisor.default_memory is less than minimum required 256, please specify a larger value: unknown
-
If you set
io.katacontainers.config.hypervisor.default_memoryto256andio.katacontainers.config.hypervisor.default_vcpusto1, the smallest instance type or instance size is launched from the list. -
If you set
io.katacontainers.config.hypervisor.default_vcpusto0, all annotations are ignored and the default instance is launched.
Workaround: Set io.katacontainers.config.hypervisor.machine_type to the default AWS instance type or Azure instance size specified in the config map to enable flexible pod VM sizes.
Jira:KATA-2575, Jira:KATA-2578, Jira:KATA-2577
