|
14 | 14 | - [Current Services NodePort allocation model](#current-services-nodeport-allocation-model)
|
15 | 15 | - [Proposed Services NodePorts allocation model](#proposed-services-nodeports-allocation-model)
|
16 | 16 | - [Test Plan](#test-plan)
|
| 17 | + - [Prerequisite testing updates](#prerequisite-testing-updates) |
17 | 18 | - [Unit tests](#unit-tests)
|
| 19 | + - [Integration tests](#integration-tests) |
| 20 | + - [e2e tests](#e2e-tests) |
18 | 21 | - [Graduation Criteria](#graduation-criteria)
|
19 | 22 | - [Alpha](#alpha)
|
20 | 23 | - [Beta](#beta)
|
@@ -273,17 +276,21 @@ Example 3 Small service nodeport range:
|
273 | 276 |
|
274 | 277 | ### Test Plan
|
275 | 278 |
|
276 |
| -This feature doesn't modify the cluster behavior, only the order on which dynamic port are assigned to NodePort Services, |
277 |
| -there is no need for e2e or integration tests, unit tests are enough. |
278 |
| -
|
279 | 279 | [x] I/we understand the owners of the involved components may require updates to
|
280 | 280 | existing tests to make this code solid enough prior to committing the changes necessary
|
281 | 281 | to implement this enhancement.
|
282 | 282 |
|
| 283 | +##### Prerequisite testing updates |
| 284 | +None |
283 | 285 |
|
284 | 286 | ##### Unit tests
|
| 287 | +- `kubernetes/pkg/registry/core/service/portallocator`: `12/10/2022` - `83.1` |
| 288 | +
|
| 289 | +##### Integration tests |
285 | 290 |
|
286 |
| -- pkg/registry/core/service/portallocator/allocator_test.go - 83.1 |
| 291 | +This feature doesn't modify the cluster behavior, only the order on which dynamic port are assigned to NodePort Services, there is no need for e2e or integration tests, unit tests are enough. |
| 292 | +
|
| 293 | +##### e2e tests |
287 | 294 |
|
288 | 295 | ### Graduation Criteria
|
289 | 296 |
|
|
438 | 445 | ###### Will enabling / using this feature result in non-negligible increase of resource usage (CPU, RAM, disk, IO, ...) in any components?
|
439 | 446 |
|
440 | 447 | No
|
| 448 | +
|
| 449 | +###### Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)? |
| 450 | +
|
| 451 | +No |
| 452 | +
|
441 | 453 | ### Troubleshooting
|
442 | 454 |
|
443 | 455 | ###### How does this feature react if the API server and/or etcd is unavailable?
|
|
0 commit comments