unable to create pods after setting resources#29416
unable to create pods after setting resources#29416mburke5678 merged 1 commit intoopenshift:masterfrom
Conversation
openshift-ci-robot
added
the
size/S
|
Deploy preview for osdocs ready! Built with commit 715d784 |
mburke5678
requested review from
aburdenthehand,
codyhoag,
jeana-redhat and
vikram-redhat
as code owners
openshift-ci-robot
added
size/XS
|
@sunilcio PTAL. Thanks!! |
|
@mburke5678 thanks, lgtm |
mburke5678
force-pushed
the
BZ-1705322
branch
from
ba59722 to
c9e7f3d
Compare
|
@umohnani8 Which OpenShift versions does this change apply to? It looks like the code change went into 4.6. Was it back ported to 4.5 or 4.4? Thank you! |
mburke5678
force-pushed
the
BZ-1705322
branch
from
c9e7f3d to
62018f1
Compare
mburke5678
added
the
peer-review-needed
kalexand-rh
left a comment
kalexand-rh
left a comment
There was a problem hiding this comment.
This is looking good!
There was a problem hiding this comment.
| The minimum memory limit for a depoyment is 12 MB. If a container fails to start due to a `Cannot allocate memory` pod event, the memory limit is too low. You should either increase or remove the memory limit. Removing the limit allows pods to consume unbounded node resources. | |
| The minimum memory limit for a deployment is 12 MB. If a container fails to start due to a `Cannot allocate memory` pod event, the memory limit is too low. Either increase or remove the memory limit. Removing the limit allows pods to consume unbounded node resources. |
There was a problem hiding this comment.
| You should either increase or remove the memory limit. Removing the limit allows pods to consume unbounded node resources. | |
| Either increase or remove the memory limit. Removing the limit allows pods to consume unbounded node resources. |
kalexand-rh
added
peer-review-done
mburke5678
force-pushed
the
BZ-1705322
branch
from
62018f1 to
715d784
Compare
|
@mburke5678 this change should be available in 4.4 and 4.5 as well. The cri-o PR made it in before cri-o 1.15 was cut. |
|
/cherrypick enterprise-4.5 |
|
@mburke5678: new pull request created: #29820 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/cherrypick enterprise-4.6 |
|
/cherrypick enterprise-4.7 |
|
/cherrypick enterprise-4.8 |
|
@mburke5678: new pull request created: #29821 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@mburke5678: new pull request created: #29822 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@mburke5678: new pull request created: #29823 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
6 participants
https://bugzilla.redhat.com/show_bug.cgi?id=1705322