Therefore, I would recommend scaling down the base OpenShift installation so that it releases more resources for Ansible Tower. It is the Ansible Tower pod that has the most demand on the resources. However, the PostgreSQL pod is not really very demanding on resources. One way to avoid resource demands might be to spin up PostgreSQL outside of OpenShift using a Docker image or external system. This was the minimum needed to get the Ansible Tower login and be able to navigate around the application. We will use these settings going forward but feel free to increase them to handle even more demands from Ansible Tower and PostreSQL. Therefore, the recommended minimum resource settings for CRC to handle the Ansible Tower installation are the following: Oc describe pod ansible-tower | grep Warning With the default settings OpenShift cannot start the tower pod and shows a Pending status with the reason stating “0/1 nodes are available: 1 Insufficient cpu, 1 Insufficient memory.” To check this on your laptop, after Tower installer is completed use the following commands: As a result, it is not possible to install Ansible Tower and PostgreSQL within the OpenShift cluster using the default resource settings (cpu and memory) as they were insufficient. 20 GB of storage (due to Ansible Tower requirements)ĬRC creates a virtual machine with an OpenShift installation that already consumes a lot of the available resources.PostgreSQL has the following minimum requirements: Linux: Red Hat Enterprise Linux 7.5, CentOS 7.5, or latest two stable Fedora releasesĪnsible Tower has the following minimum requirements:.Microsoft Windows: Windows 10 Fall Creators Update (version 1709) or newer.This may cause other differences, particularly with external networking.ĬodeReady Containers (CRC) has the following minimum requirements: The OpenShift instance runs in a virtual machine.For the same reason, there is no upgrade path to newer OpenShift versions.These disabled Operators cause the corresponding parts of the web console to be non-functional.It disables the machine-config and monitoring Operators by default.It uses a single node which behaves as both a master and worker node. ![]()
0 Comments
Leave a Reply. |