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

Keep track of k8s api server usage #53

Closed
yaron2 opened this issue Mar 26, 2019 · 7 comments
Closed

Keep track of k8s api server usage #53

yaron2 opened this issue Mar 26, 2019 · 7 comments
Labels
enhancement New feature or request integration:kubernetes All issues related to integrating with Kubernetes stale All issues that are marked as stale due to inactivity

Comments

@yaron2
Copy link
Contributor

yaron2 commented Mar 26, 2019 •
edited

This issue is to examine KEDA's CPU and Memory implications in regards to the Kubernetes API server.
This is to ensure that KEDA does not cause over-utilization of the API server, as it communicates in a bi-di manner with the API server (KEDA controller being asked for metrics and looking up Kubernetes objects using the Kubernetes API).
@tomkerkhove
Copy link
Member

@yaron2 can you provide some info on this issue please?

@yaron2
Copy link
Contributor Author

yaron2 commented May 4, 2020

Updated the description.

@zroubalik
Copy link
Member

We should set limits on the containers as well.

@yaron2
Copy link
Contributor Author

yaron2 commented May 4, 2020

@zroubalik yes that's a must. a potential memory leak or CPU hog in KEDA should not drain the node running it.

@tomkerkhove
Copy link
Member

Great, thanks for the update!

@tomkerkhove tomkerkhove added enhancement New feature or request integration:kubernetes All issues related to integrating with Kubernetes labels May 4, 2020
@zroubalik zroubalik mentioned this issue Jul 8, 2020
Merged
@stale
Copy link

stale bot commented Oct 13, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Oct 13, 2021
@stale
Copy link

stale bot commented Oct 20, 2021

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Oct 20, 2021
preflightsiren pushed a commit to preflightsiren/keda that referenced this issue Nov 7, 2021
@iyacontrol @jeffhollan
add sasl auth for kafka (kedacore#53)
1071e04 
* add sasl auth for kafka

* pdate sasl auth info reference a secret

* add sasl_ssl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request integration:kubernetes All issues related to integrating with Kubernetes stale All issues that are marked as stale due to inactivity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@zroubalik @tomkerkhove @yaron2