Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

kubernetes-image-puller-operator 1.0.0 is in the CrashLoopBackOff State due to low memory limits #21448

Closed
Tracked by #21438
ibuziuk opened this issue Jun 8, 2022 · 6 comments · Fixed by che-incubator/kubernetes-image-puller-operator#79
Closed
Tracked by #21438

kubernetes-image-puller-operator 1.0.0 is in the CrashLoopBackOff State due to low memory limits #21448

ibuziuk opened this issue Jun 8, 2022 · 6 comments · Fixed by che-incubator/kubernetes-image-puller-operator#79
Assignees
@dkwon17
Labels
area/image-puller Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jun 8, 2022 •
edited
Loading

Describe the bug

image

Che version

other (please specify in additional context)

Steps to reproduce

Install 1.0.0 image puller on a cluster with 100+ namespaces
ERROR: Operator pod is crashing

Expected behavior

Operator pod is running without errors

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Amazon

Eclipse Che Logs

No response

Additional context

Probably the limits are low:

Resource requests
cpu: 100m, memory: 64Mi
Resource limits
cpu: 100m, memory: 128Mi
@ibuziuk ibuziuk added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. area/image-puller Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller labels Jun 8, 2022
@ibuziuk ibuziuk mentioned this issue Jun 8, 2022
Closed
64 tasks
@dkwon17 dkwon17 mentioned this issue Jun 22, 2022
Merged
@ibuziuk
Copy link
Member Author

ibuziuk commented Jun 23, 2022

Should be fixed in the 1.0.1 upcoming release

@ibuziuk ibuziuk reopened this Aug 1, 2022
@ibuziuk
Copy link
Member Author

ibuziuk commented Aug 1, 2022

looks like current limits are not enough for large clusters. Installation failed on the developer sandbox. As a workaround the memory limit in csv has been updated to 1Gi

image

@ibuziuk
Copy link
Member Author

ibuziuk commented Aug 1, 2022

@dkwon17 I believe we need to release 1.0.2 with more generous limits for operator

@ibuziuk
Copy link
Member Author

ibuziuk commented Aug 2, 2022

According to the metrics we probably need to set it to 1Gi to be on the safe side. During the startup there is a spike, but then RAM consumption drops to ~ 400M

image

@dkwon17 dkwon17 mentioned this issue Aug 2, 2022
Merged
@dkwon17
Copy link
Contributor

dkwon17 commented Aug 2, 2022

@ibuziuk I made a PR: che-incubator/kubernetes-image-puller-operator#83

@ibuziuk
Copy link
Member Author

ibuziuk commented Aug 16, 2022

Fixed in 1.0.2 version https://operatorhub.io/operator/kubernetes-imagepuller-operator
Closing

@ibuziuk ibuziuk closed this as completed Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkwon17 dkwon17

Labels
area/image-puller Issues related to image-puller https://github.com/che-incubator/kubernetes-image-puller kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: update memory limit dkwon17/kubernetes-image-puller-operator
2 participants
@ibuziuk @dkwon17