CRC is a tool to help you run containers. It manages a local OpenShift 4.x cluster, Microshift or a Podman VM optimized for testing and development purposes
# Put the output of `crc version`
crc version: 1.11.0+883ca49
OpenShift version: 4.4.5 (embedded in binary)
CRC status
# Put the output of `crc status`
CRC VM: Running
OpenShift: Running (v4.4.5)
Disk Usage: 16.48GB of 32.72GB (Inside the CRC VM)
Cache Usage: 12.12GB
Cache Directory: /Users/eschabel/.crc/cache
CRC config
# Put the output of `crc config view`
- cpus : 4
- memory : 12288
- pull-secret-file : /Users/eschabel/bin/pull-secret.txt
Host Operating System
# put the output of `sw_vers` in case of Mac
ProductName: Mac OS X
ProductVersion: 10.15.4
BuildVersion: 19E287
watch them spin up the pods and depending on order, one of the three pods will fail with "0/1 nodes are available: 1 Insufficient memory."
Expected
That all pods spin up and deploy.... why does this developer experience CRC based on OCP 4.4 need 12 GB and the basic product images can't be used for a web front-end app on EAP and RHDM decision service backend?
This project was used succesfully on OCP 3.x with 3-6GB of memory.
Actual
Something should be done to provide a developer experience on their local machine that can run with a lot less memory.
Logs
Out of memory errors kills attempts to get you logs. See attached screenshots.
General information
crc setup
before starting it (Yes)?CRC version
CRC status
CRC config
Host Operating System
Steps to reproduce
Expected
That all pods spin up and deploy.... why does this developer experience CRC based on OCP 4.4 need 12 GB and the basic product images can't be used for a web front-end app on EAP and RHDM decision service backend?
This project was used succesfully on OCP 3.x with 3-6GB of memory.
Actual
Something should be done to provide a developer experience on their local machine that can run with a lot less memory.
Logs
Out of memory errors kills attempts to get you logs. See attached screenshots.