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
High memory usage #149
Comments
Its a shame there are not default values included for the resources requests/limits in the helm chart. |
👍 , same here. My pod reaches 1GB in two days. And finally:
|
Bueller... Bueller... (sigh) Dear 1password: Hello. You might remember me from January 4th of this year. (I think I tripped over @robb-j's corpse in the parking lot, but, no matter, I'm here now). This isn't an open-source project in so much as anyone using it is a paying customer or works for a paying customer. If this operator should be considered abandoned, please have the courtesy of letting us know so we can make other arrangements. Thanks |
Second the motion. |
Hey @gladiatr72! Samira here from 1Password 👋🏻 Thanks for bringing this to our attention. We do keep a close eye on all of our repos and this issue in particular hasn't been forgotten. Memory issues tend to be tricky and we've been working on our end to try to figure this one out. Apologies on not keeping the issue updated, but it has not been forgotten. To alleviate your concerns about this repo being abandoned, I want to stress that this is not the case. We are actively working on it and in fact, we released a new version last month that addressed a few bugs. Here are the release notes on that particular release. We'll continue making updates to this repo over time and will keep the issue updated with our progress on this memory issue. Thanks! |
I'm starting to feel a bit neglected again... |
Your environment
Operator Version: 1.5.7
Connect Server Version: 1.5.7?
Kubernetes Version: v1.23.14
What happened?
The memory usage of my
onepassword-connect
pod was 1097Mi which seems very high, is there a normal amount of memory this container should stay around?What did you expect to happen?
I thought the container would need a lot less memory
Steps to reproduce
This is on a really small cluster with only 8 OnePasswordItem resources in it.
Mi
every few minuteNotes & Logs
before restarting
after restarting
my
values.yml
passed to helm:The text was updated successfully, but these errors were encountered: