Skip to content
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.

Commit

Permalink
Merge pull request #1306 from yiqigao217/e2e
Browse files Browse the repository at this point in the history
Increase memory limits and requests and update docs
  • Loading branch information
k8s-ci-robot authored Dec 7, 2020
2 parents 979068d + 6e62f38 commit 0a46538
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 2 deletions.
4 changes: 2 additions & 2 deletions incubator/hnc/config/manager/manager.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -49,8 +49,8 @@ spec:
resources:
limits:
cpu: 100m
memory: 100Mi
memory: 300Mi
requests:
cpu: 100m
memory: 50Mi
memory: 150Mi
terminationGracePeriodSeconds: 10
12 changes: 12 additions & 0 deletions incubator/hnc/docs/user-guide/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,18 @@ limitations. You can adjust the `--apiserver-qps-throttle` parameter in the
manifest to increase it from the default of 50qps if your cluster supports
higher values.

## How much memory does HNC need?

As of Dec. 2020, the [HNC performance test](../../scripts/performance/README.md)
shows that 700 namespaces with 10 propagatable objects in each namespace would
use about 200M memory during HNC startup and about 150M afterwards. Thus, we set
a default of 300M memory limits and 150M memory requests for HNC.

To change HNC memory limits and requests, you can update the values in
`config/manager/manager.yaml`, run `make manifests` and reapply the manifest. If
you are using a GKE cluster, you can view the real-time memory usage in the
`Workloads` tab and determine what's the best limits and requests for you.

## Does HNC support high-availability?

HNC is currently deployed as a single in-memory pod and therefore does not
Expand Down

0 comments on commit 0a46538

Please sign in to comment.