[QA integration tests] Opensearch pods can't be scheduled on nodes due to insufficient cpu resources on public AWS

[andrewluckyguy]

Describe the bug

We've tried to deploy Opensearch service to the https://eed97a9ea4d698641aac638d85b7a273.gr7.us-east-1.eks.amazonaws.com.
It is needed for the automation of deployment via GitHub workflow, where a runner would be used on the AWS cloud:
Netcracker/qubership-opensearch#53 (comment)

Opensearch pods can't start:

opensearch        opensearch-0                                          0/1     Pending            0                134m
opensearch        opensearch-1                                          0/1     Pending            0                156m
opensearch        opensearch-2                                          0/1     Pending            0                4h31m
opensearch        opensearch-dashboards-55d55ccb5c-fkddr                1/1     Running            0                4d21h
opensearch        opensearch-integration-tests-675895578d-bpmcp         1/1     Running            20 (3m33s ago)   136m
opensearch        opensearch-service-operator-b6ffbc975-682wd           1/1     Running            0                6h44m

Namespace events:

# kubectl get events -n opensearch
LAST SEEN   TYPE      REASON             OBJECT                                              MESSAGE
10m         Warning   FailedScheduling   pod/opensearch-0                                    0/4 nodes are available: 1 Too many pods, 2 Insufficient cpu, 2 node(s) had volume node affinity conflict. preemption: 0/4 nodes are available: 2 No preemption victims found for incoming pod, 2 Preemption is not helpful for scheduling.
10m         Warning   FailedScheduling   pod/opensearch-1                                    0/4 nodes are available: 1 Too many pods, 2 Insufficient cpu, 2 node(s) had volume node affinity conflict. preemption: 0/4 nodes are available: 2 No preemption victims found for incoming pod, 2 Preemption is not helpful for scheduling.
10m         Warning   FailedScheduling   pod/opensearch-2                                    0/4 nodes are available: 1 Too many pods, 2 Insufficient cpu, 2 node(s) had volume node affinity conflict. preemption: 0/4 nodes are available: 2 No preemption victims found for incoming pod, 2 Preemption is not helpful for scheduling.

The following configuration was used
https://github.com/Netcracker/qubership-test-pipelines/blob/test_opensearch/templates/opensearch-service/opensearch_clean_all_on_sc.yml#L23

To Reproduce

Deploy Opensearch application using helm install

Version

No response

Logs

No response

Additional information

No response

[RomanB89]

Corrected node amount in aws - now all pods are up&running
NAME READY STATUS RESTARTS AGE
opensearch-0 1/1 Running 0 19h
opensearch-1 1/1 Running 0 29m
opensearch-2 1/1 Running 0 14h
opensearch-dashboards-55d55ccb5c-jxp8r 1/1 Running 0 2m48s
opensearch-integration-tests-675895578d-mc2m7 1/1 Running 0 2m23s
opensearch-service-operator-b6ffbc975-h7bm8 1/1 Running 0 2m48s