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.

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

Sidecar -reports generator configuration #328

Closed
andrewazores opened this issue Jan 11, 2022 · 0 comments · Fixed by #325
Closed

Sidecar -reports generator configuration #328

andrewazores opened this issue Jan 11, 2022 · 0 comments · Fixed by #325
Assignees
Labels
feat New feature or request
Milestone

Comments

@andrewazores
Copy link
Member

andrewazores commented Jan 11, 2022

Closes #277 (obsolete)

The Operator should have a way to configure deployment of -reports as sidecar containers alongside the main Cryostat instance. If the configuration is set up for 0 sidecars then the overall configuration should be essentially identical to how it is now, with the main Cryostat instance performing subprocess report generation. If >0 sidecars are configured then a deployment should be created with the corresponding number of replicas, with configured resource (CPU/mem) requests+limits, and an internal-traffic-only Service in front of the sidecars, with the main Cryostat instance configured to use remote report generation pointed at the Service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants