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

Implement Resource Configuration for Jobs in volsync-rsync-tls-src #1058

Closed
Sanjeeth8733 opened this issue Jan 9, 2024 · 1 comment
Closed
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@Sanjeeth8733
Copy link

Sanjeeth8733 commented Jan 9, 2024

Currently, the volsync-rsync-tls-src jobs lack resource configuration. We propose adding configurable resource values to enhance control and optimization of resource utilization for these jobs.

Users will benefit from improved resource management for volsync-rsync-tls-src jobs, allowing for better customization based on specific requirements. This enhancement is a priority as it enhances overall system performance and efficiency.

Acceptance Criteria:

The volsync-rsync-tls-src jobs must have configurable resource values.
Resource values should follow the specified format:

`
resources:
requests:
memory:
cpu:
limits:
memory:
cpu:

`
Replace with the desired memory value and with the desired CPU value.
Users can easily customize resource values to meet their specific requirements.
Additional context:

Currently, the lack of resource configuration limits the ability to optimize performance for volsync-rsync-tls-src jobs. The proposed solution will enhance flexibility and resource utilization, contributing to overall system efficiency.

@Sanjeeth8733 Sanjeeth8733 added the enhancement New feature or request label Jan 9, 2024
@JohnStrunk JohnStrunk added the duplicate This issue or pull request already exists label Jan 9, 2024
@JohnStrunk
Copy link
Member

Duplicate of #707

@JohnStrunk JohnStrunk marked this as a duplicate of #707 Jan 9, 2024
@JohnStrunk JohnStrunk closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
Archived in project
Development

No branches or pull requests

2 participants