![]() Automatic merge from submit-queue (batch tested with PRs 50806, 48789, 49922, 49935, 50438) iSCSI volume plugin: iSCSI initiatorname support **What this PR does / why we need it**: This PR adds iSCSI initiatorname parameter to ISCSIVolumeSource to enable automatic configuration of initiator name per volume. This would allow for more fine grained configuration, and remove the need to configure the initiator name on the host by administrator. **Which issue this PR fixes**: fixes #47311 **Special notes for your reviewer**: /cc @rootfs @jsafrane @msau42 **Release note**: ``` iSCSI volume plugin: Support customization of iSCSI initiator name per volume ``` |
||
---|---|---|
.. | ||
src/k8s.io | ||
BUILD | ||
OWNERS | ||
README.md | ||
godeps-json-updater.go | ||
prime-apimachinery.sh |
README.md
External Repository Staging Area
This directory is the staging area for packages that have been split to their own repository. The content here will be periodically published to respective top-level k8s.io repositories.
Repositories currently staged here:
k8s.io/apiextensions-apiserver
k8s.io/api
k8s.io/apimachinery
k8s.io/apiserver
k8s.io/client-go
k8s.io/kube-aggregator
k8s.io/code-generator
(about to be published)k8s.io/metrics
k8s.io/sample-apiserver
The code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code.
Using staged repositories from Kubernetes code
Kubernetes code uses the repositories in this directory via symlinks in the
vendor/k8s.io
directory into this staging area. For example, when
Kubernetes code imports a package from the k8s.io/client-go
repository, that
import is resolved to staging/src/k8s.io/client-go
relative to the project
root:
// pkg/example/some_code.go
package example
import (
"k8s.io/client-go/dynamic" // resolves to staging/src/k8s.io/client-go/dynamic
)
Once the change-over to external repositories is complete, these repositories
will actually be vendored from k8s.io/<package-name>
.