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

e2e storage: disable health-monitor controller in hostpath deployment

Browse Source 
This reverts commit
c15fd76ee9. Most (all?) of the hostpath
tests and several other tests started to fail again in
gce-scale-master-correctness after re-enabling the controller. This
shows that it was not just the obsolete agent which causes scalability
problems, but also the controller.

It has to be disabled until the scalability problems are addressed.
This commit is contained in:
Patrick Ohly 2021-06-08 20:19:52 +02:00
parent 5a21b97882
commit 528baa09f6
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
test/e2e/storage/drivers/csi.go
View File

@ -242,16 +242,19 @@ func (h *hostpathCSIDriver) PrepareTest(f *framework.Framework) (*storageframewo
return err
}
// Remove csi-external-health-monitor-agent because it is
// obsolete and shouldn't have been deployed by csi-driver-host-path v1.7.2.
// This can be removed when updating to a newer driver that
// doesn't deploy the agent.
// Remove csi-external-health-monitor-agent and
// csi-external-health-monitor-controller
// containers. The agent is obsolete.
// The controller is not needed for any of the
// tests and is causing too much overhead when
// running in a large cluster (see
// https://github.com/kubernetes/kubernetes/issues/102452#issuecomment-856991009).
switch item := item.(type) {
case *appsv1.StatefulSet:
var containers []v1.Container
for _, container := range item.Spec.Template.Spec.Containers {
switch container.Name {
case "csi-external-health-monitor-agent":
case "csi-external-health-monitor-agent", "csi-external-health-monitor-controller":
// Remove these containers.
default:
// Keep the others.