Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue a50ea2fc37 Merge pull request #41196 from bigstepinc/master
Automatic merge from submit-queue

Fix for Premature iSCSI logout #39202.

**What this PR does / why we need it**:

Modifies the iSCSI volume plugin code to prevent premature iSCSI logouts and the establishment of multiple iSCSI connections to the same target in certain cases.

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #39202, fixes #41041, fixes #40941

**Special notes for your reviewer**:

The existing iSCSI connections are now rescanned on every AttachDisk call to discover newly created LUNs.

The disk mount points now contain an additional directory in the path corresponding to the disk iface that is later used for iSCSI logout.

The device prefixes that are used to count the existing references to the portal-target pair now contain the whole path including the mount point until the lun index.

**Release note**:
```release-note
Fixed issues #39202, #41041 and #40941 that caused the iSCSI connections to be prematurely closed when deleting a pod with an iSCSI persistent volume attached and that prevented the use of newly created LUNs on targets with preestablished connections.
```
2017-02-15 04:11:55 -08:00
.github Fix issue template to read more clearly 2017-01-27 10:15:06 -07:00
api Merge pull request #41184 from liggitt/subject-apigroup 2017-02-13 21:07:10 -08:00
build remove kube-aggregator from bazel until we can build it 2017-02-14 14:57:52 -05:00
cluster Merge pull request #41211 from enisoc/configure-audit-log 2017-02-15 03:25:12 -08:00
cmd Merge pull request #41413 from deads2k/agg-13-move 2017-02-14 19:54:11 -08:00
docs Merge pull request #41184 from liggitt/subject-apigroup 2017-02-13 21:07:10 -08:00
examples Merge pull request #41383 from liggitt/v1beta1-cleanup 2017-02-14 22:35:05 -08:00
federation Merge pull request #41243 from shashidharatd/kubefed-1 2017-02-15 03:25:13 -08:00
Godeps Update generated files 2017-01-29 21:41:45 +01:00
hack Merge pull request #41211 from enisoc/configure-audit-log 2017-02-15 03:25:12 -08:00
hooks
logo Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
pkg Merge pull request #41196 from bigstepinc/master 2017-02-15 04:11:55 -08:00
plugin Merge pull request #41285 from liggitt/kube-scheduler-role 2017-02-15 03:25:10 -08:00
staging Create bootstrap system:kube-scheduler role 2017-02-15 01:05:42 -05:00
test Merge pull request #41285 from liggitt/kube-scheduler-role 2017-02-15 03:25:10 -08:00
third_party Update generated files 2017-01-25 19:49:45 +01:00
translations Extract strings for translation. 2017-02-06 22:32:01 -08:00
vendor Merge pull request #41413 from deads2k/agg-13-move 2017-02-14 19:54:11 -08:00
.bazelrc Add verify-gofmt as a Bazel test. 2017-02-10 17:00:28 -08:00
.gazelcfg.json Generate a dummy BUILD file in _output/local/go to keep Bazel out of trouble 2017-01-05 22:05:17 -08:00
.generated_docs Added generated docs for kubectl create role command. 2017-02-10 13:10:47 +08:00
.generated_files
.gitattributes
.gitignore
BUILD.bazel bazel: save git version in kubernetes.tar.gz 2017-01-23 17:28:08 -08:00
CHANGELOG.md Update CHANGELOG.md for v1.5.3. 2017-02-15 00:47:03 -08:00
code-of-conduct.md
CONTRIBUTING.md
labels.yaml
LICENSE
Makefile Add verify-gofmt as a Bazel test. 2017-02-10 17:00:28 -08:00
Makefile.generated_files
OWNERS Add wojtec to global approvers 2017-01-25 11:57:00 -06:00
OWNERS_ALIASES OWNERS: Create sig-node alias 2017-01-17 16:25:40 -08:00
README.md Tidy up the main README. 2017-02-01 20:13:09 -08:00
Vagrantfile
WORKSPACE upgrade to latest build rules 2017-02-01 15:16:43 -08:00

Kubernetes

Submit Queue Widget GoDoc Widget

Introduction

Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications. Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF).

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.


Are you ...

Code of Conduct

The Kubernetes community abides by the CNCF code of conduct. Here is an excerpt:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

Community

Do you want to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented?. If you are a company, you should consider joining the CNCF. For details about who's involved in CNCF and how Kubernetes plays a role, read the announcement. For general information about our community, see the website community page.

Contribute

If you're interested in being a contributor and want to get involved in developing Kubernetes, get started with this reading:

You will then most certainly gain a lot from joining a SIG, attending the regular hangouts as well as the community meeting.

If you have an idea for a new feature, see the Kubernetes Features repository for a list of features that are coming in new releases as well as details on how to propose one.

Building Kubernetes for the impatient

If you want to build Kubernetes right away there are two options:

$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
$ git clone https://github.com/kubernetes/kubernetes
$ cd kubernetes
$ make quick-release

If you are less impatient, head over to the developer's documentation.

Support

While there are many different channels that you can use to get hold of us (Slack, Stack Overflow, Issues, Forums/Mailing lists), you can help make sure that we are efficient in getting you the help that you need.

If you need support, start with the troubleshooting guide and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another. We don't bite!

Analytics