-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Improvement
-
False
-
None
-
False
-
OCPSTRAT-1251 - HCP: Guest clusters should support up to 500 worker nodes
-
-
-
Hypershift Sprint 257, Hypershift Sprint 258, Hypershift Sprint 259, Hypershift Sprint 260, Hypershift Sprint 261, Hypershift Sprint 262
-
0
-
0
-
0
User Story:
As a service provider, I want to be able to:
- Configure priority and fairness settings per HostedCluster size and force these settings to be applied on the resulting hosted cluster.
so that I can achieve
- Prevent user of hosted cluster from bringing down the HostedCluster kube apiserver with their workload.
Acceptance Criteria:
Description of criteria:
- HostedCluster priority and fairness settings should be configurable per cluster size in the ClusterSizingConfiguration CR
- Any changes in priority and fairness inside the HostedCluster should be prevented and overridden by whatever is configured on the provider side.
- With the proper settings, heavy use of the API from user workloads should not result in the KAS pod getting OOMKilled due to lack of resources.
This does not require a design proposal.
This does not require a feature gate.
- blocks
-
HOSTEDCP-1895 [release-4.16] Add support for configuring maximum requests in flight
- To Do
- is cloned by
-
HOSTEDCP-1895 [release-4.16] Add support for configuring maximum requests in flight
- To Do
- relates to
-
HOSTEDCP-1706 Metric tracking clusters with overriden autoscaling via HOSTEDCP-1697
- Code Review
-
HOSTEDCP-1309 Spike on Priority/Fairness configuration for k8s API server
- Closed
- links to
(2 links to)