Skip to content

Don't force limits or resources when not pinning CPUs #2471

Open
@mflendrich

Description

@mflendrich

Issue originally authored by tnozicka as #414

It's a common practice in Kubernetes to define only requests and no limits so the payload can grow with the dataset or number of users. Fixed limits prevent it. Unless we are pinning CPUs we should be user friendly and honor the ask. Also in kube resources are optional while our CRD has them required.

https://github.com/scylladb/scylla-operator/blob/master/pkg/api/v1/cluster_validation.go#L60-62

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/from-migrationIndicates that this issue is a copy of a corresponding issue mentioned in the description.priority/backlogHigher priority than priority/awaiting-more-evidence.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions