StarlingX Harbor app
5187c76f47
This adjustment is part of a proposed solution to address high CPU usage on the platform. Currently, Harbor pods are configured with timeoutSeconds=1 and failureThreshold=2 for several probes. However, the recommended values are timeoutSeconds=5 seconds or more and failureThreshold=3 or more. Other parameters, such as successThreshold and periodSeconds, already meet the recommended settings. This review updates the timeoutSeconds to 5 seconds and failureThreshold to 3 wherever these values were previously set to less than 3. Test Plan: PASS: build-pkgs && build-image PASS: AIO-SX app upload/apply/remove/delete PASS: AIO-SX Verify if the Liveness probes parameters are configured as follows: timeoutSeconds: 5 failureThreshold: <3 or more> successThreshold: 1 periodSeconds: 10 PASS: AIO-SX verify if harbor login page is accessibe and 'admin' user is able to login to harbor registry Story: 2010721 Task: 50933 Change-Id: I0031d792a3dd156702795c60d61afaf19c7e317d Signed-off-by: Jagatguru Prasad Mishra <jagatguruprasad.mishra@windriver.com> |
||
---|---|---|
helm-charts/upstream/harbor-helm | ||
python3-k8sapp-harbor | ||
stx-harbor-helm | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
debian_build_layer.cfg | ||
debian_iso_image.inc | ||
debian_pkg_dirs | ||
HACKING.rst | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |