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

Splunk Operator: SearchHeadCluster CustomResourceDefinition - Please provide a way to apply different resource limits and affinity to the deployer instance #1307

Open
gjanders opened this issue Mar 8, 2024 · 1 comment
Assignees
Labels
deployer-crd enhancement New feature or request

Comments

@gjanders
Copy link
Contributor

gjanders commented Mar 8, 2024

Please select the type of request

Bug

Tell us more

Describe the request

Currently the CustomResourceDefinition for the kind: SearchHeadCluster does not provide a way to provide different configuration between the deployer and search head cluster members.

Expected behavior

For the indexing tier we have 2 unique CRD's, (kind: IndexerCluster and kind: ClusterManager).
I'd like a solution like this for the Deployer and SearchHeadCluster, alternatively at least the ability to control the affinity settings and the request limits (cpu/memory)

Splunk setup on K8S
N/A

Reproduction/Testing steps
N/A

K8s environment
N/A

Proposed changes(optional)
Provide a unique CRD for the Deployer and SearchHeadCluster
Or an alternative option to achieve this goal

K8s collector data(optional)
N/A

Additional context(optional)
I do notice:
# 1048
# 459
# 1138

Are similar, although my request is specifically around resource limits and affinity. However any "fix" will (hopefully) resolve all the issues mentioned

@gjanders
Copy link
Contributor Author

gjanders commented Mar 8, 2024

While this seems to file as a bug by default, it's more of an enhancement request

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

No branches or pull requests

4 participants