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

Hotfix - brokers should use a split client (read -> cache, write -> direct) to avoid compute resource usage spikes #1156

Open
balpert89 opened this issue Nov 18, 2024 · 1 comment · May be fixed by #1165
Open

Hotfix - brokers should use a split client (read -> cache, write -> direct) to avoid compute resource usage spikes #1156

balpert89 opened this issue Nov 18, 2024 · 1 comment · May be fixed by #1165
Labels
bug Something isn't working

Comments

@balpert89
Copy link
Contributor

See onmetal/onmetal-api@415f563#diff-6fab650482a4150db58cd8f3641208cde1da3b12131681dca752ce399d21ac40 as a hotfix. controller-runtime also mentions split clients as the default case, is there a special use case which requires direct reads to the API server? See https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/client#hdr-Clients
@balpert89 balpert89 added the bug Something isn't working label Nov 18, 2024
@balpert89
Copy link
Contributor Author

Bildschirmfoto 2024-11-18 um 10 06 41

@balpert89 balpert89 linked a pull request Nov 19, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implemented a split client for *-brokers opensovereigncloud/ironcore
1 participant
@balpert89