Sean McGinnis 69a2deea9c iscsi: set node.startup to manual ...

If the default iSCSI node.startup is set to automatic, if there is a node failure,
any pods on that node will get rescheduled to another node. If the failed node is
later brought back up it will then try to log back in to any iSCSI sessions it had
prior to the failure, which may no longer exist or may be now in-use by the other
nodes.

It appears most platforms keep the open-iscsi default of node.startup-automatic.
But in case this system-wide setting has been changed, and just to be explicit, this
sets node.startup values for kubernetes controlled volumes to manual.

Closes issue #21305

2017-12-20 15:37:22 -06:00

..

attacher.go

use core client with explicit version

2017-11-25 08:14:10 +08:00

BUILD

use SecretObject to reference iSCSI CHAP secret

2017-11-18 20:02:44 +00:00

disk_manager.go

Refactoring and improvements for iSCSI and FC

2017-09-18 21:33:11 -04:00

doc.go

…

iscsi_test.go

use SecretObject to reference iSCSI CHAP secret

2017-11-18 20:02:44 +00:00

iscsi_util_test.go

…

iscsi_util.go

iscsi: set node.startup to manual

2017-12-20 15:37:22 -06:00

iscsi.go

use core client with explicit version

2017-11-25 08:14:10 +08:00

OWNERS

Update volume OWNERS to reflect active sig-storage reviewers

2017-10-26 13:26:33 -07:00