Details
-
Task
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
17: Automation, future fixes, 21: Auto., crackn' on Krakken, 23: ARM, Trackin' Kraken, 25: Maintain, 3 - Krack the whip, 4 - Operation Krack-down, 5 - Kraken Bug Fixes/Docs, 6 - Kraken Cleanup, 7 - Til the Krack of dawn, 8 - FireKracker, 9 - Krakend, 10 - Krackeverlasting, 1 - Levianthanning, 2 - LeVIAthan or LeviaTHAN, 3 - Uk Sprinting, 4 - Who killed Tommie, 5 - No, 2.4.1 isn't released, 6- Yes, 2.4.1 is get released, 1 - 2.4.2 Dev Sprint, 1 - 2.5.0 (1 of 2)
-
5
Description
Changes are coming to server about how it detects the resources available to it when running in a container; including an env variable override to emulate the old behaviour. We need to test both the now-default behaviour, and the override. (More details available in linked ticket).
Generally this will be 3 types of test:
- Checking that CB Server recognises resource limits (accessible using the /metrics endpoint)
- Checking that CB Server respects the resource limits (stress CB with pillowfight and check limits are not exceeded)
- Checking that the newly added override flag is functional
https://docs.google.com/document/d/1SjXgp914YMPpg0ynHZgT6LpoZsB00GCwh0kfrmQCLbY/edit
There are a few testplans from various teams for this feature that CND/Operator might need to help out with:
https://docs.google.com/document/d/110XGZnRDziS_vTv4-Ax0CeqOyNT8mejI5z2b5O1MB6I/edit
https://docs.google.com/document/d/1mf4mAeN61rBNxGTF_M6956xyt7F_nIpTUWGw94f7nX4/edit
Attachments
Issue Links
- depends on
-
MB-47591 Incorrect cgroup resource detection (core/memory) when running in Container / K8S
-
- Closed
-
Gerrit Reviews
| For Gerrit Dashboard: K8S-2724 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 176384,1 | K8S-2724: Container Limit Tests | 2.3.x | couchbase-operator | Status: NEW | 0 | +1 |