-
Notifications
You must be signed in to change notification settings - Fork 324
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.
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
OOM after moving to consul-k8 0.16.0 #283
Comments
Hi Fred, thanks for the issue. If you need a workaround immediately you'll need to modify these values: https://github.com/hashicorp/consul-k8s/blob/master/connect-inject/container_init.go#L14-L19 and build a custom consul-k8s image. To be clear this is a high priority issue for us and we're working on it right now. |
Sure. I will wait for your fix. |
@lkysow Can you pls provide an ETA on this fix ? |
Hey, we're actively working on it but can't provide an accurate ETA. We can get you a custom Docker image with our planned fix if that would help? |
Yes a pointed docker image with this fix is also appreciated. |
I built |
Thanks. This helps us and works |
Yes we'll update this thread once the releases are out! |
i started using your private build Now in some cases i see consul hitting oom issue. My hunch is now the lifecycle container is hitting the resource limits. const ( Appreciate if you can give a private fix [66666.794649] RSP: 002b:00007fff487b8e50 EFLAGS: 00010202 |
After moving to latest consul-k8 ver 0.16.0. I see the resource allocation limits has been added to init containers. This causes OOM in the "cp". I have attached the related logs.
Error:
Last State: Terminated
Reason: OOMKilled
Exit Code: 137
Controlled By: ReplicaSet/apiserver-6dbcb68646
Init Containers:
consul-connect-inject-init:
Container ID: docker://13f0315c75d84b4b7c58409174974bf9f4f876abc234fce595d14af1efecc4b9
Image: consul:1.8.0
Image ID: docker-pullable://consul@sha256:0e660ca8ae28d864e3eaaed0e273b2f8cd348af207e2b715237e869d7a8b5dcc
Port:
Host Port:
Command:
/bin/sh
-ec
The text was updated successfully, but these errors were encountered: