github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-16 22:53:22 +00:00
Code Issues Projects Releases Wiki Activity

Generate and format files

Browse Source 
- Run hack/update-codegen.sh
- Run hack/update-generated-device-plugin.sh
- Run hack/update-generated-protobuf.sh
- Run hack/update-generated-runtime.sh
- Run hack/update-generated-swagger-docs.sh
- Run hack/update-openapi-spec.sh
- Run hack/update-gofmt.sh

Signed-off-by: Davanum Srinivas <davanum@gmail.com>
This commit is contained in:
Davanum Srinivas
2022-07-19 20:54:13 -04:00
parent 4784b58e17
commit a9593d634c
451 changed files with 3281 additions and 2918 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
test/integration/apiserver/flowcontrol/fight_test.go
View File

@@ -40,22 +40,24 @@ import (
testclocks "k8s.io/utils/clock/testing"
)
/* fightTest configures a test of how API Priority and Fairness config
controllers fight when they disagree on how to set FlowSchemaStatus.
In particular, they set the condition that indicates integrity of
the reference to the PriorityLevelConfiguration. The scenario tested is
two teams of controllers, where the controllers in one team set the
condition normally and the controllers in the other team set the condition
to the opposite value.
/*
fightTest configures a test of how API Priority and Fairness config
This is a behavioral test: it instantiates these controllers and runs them
almost normally. The test aims to run the controllers for a little under
2 minutes. The test takes clock readings to get upper and lower bounds on
how long each controller ran, and calculates consequent bounds on the number
of writes that should happen to each FlowSchemaStatus. The test creates
an informer to observe the writes. The calculated lower bound on the
number of writes is very lax, assuming only that one write can be done
every 10 seconds.
controllers fight when they disagree on how to set FlowSchemaStatus.
In particular, they set the condition that indicates integrity of
the reference to the PriorityLevelConfiguration. The scenario tested is
two teams of controllers, where the controllers in one team set the
condition normally and the controllers in the other team set the condition
to the opposite value.
This is a behavioral test: it instantiates these controllers and runs them
almost normally. The test aims to run the controllers for a little under
2 minutes. The test takes clock readings to get upper and lower bounds on
how long each controller ran, and calculates consequent bounds on the number
of writes that should happen to each FlowSchemaStatus. The test creates
an informer to observe the writes. The calculated lower bound on the
number of writes is very lax, assuming only that one write can be done
every 10 seconds.
*/
type fightTest struct {
t *testing.T