kubernetes

mirror of https://github.com/k3s-io/kubernetes.git synced 2025-11-01 22:34:14 +00:00

Files

Kubernetes Submit Queue c9842a2145 Merge pull request #49318 from dims/bail-on-block-storage-api-detection

Automatic merge from submit-queue (batch tested with PRs 49081, 49318, 49219, 48989, 48486)

Better message if we dont find appropriate BlockStorage API

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

With latest devstack, v1 and v2 are DEPRECATED and v3 is marked
as CURRENT. So we fail to attach the disk, the error message is
shown when one does "kubectl describe pod" but the operator has
to dig into find the problem.

So log a better message if we can't find the appropriate version
of the API that we support with an explicit error message that
the operator can see how to fix the situation.

Note support for v3 block storage API is being added to gophercloud
and will take a bit of time before we can support it.


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

**Special notes for your reviewer**:

**Release note**:

```release-note
NONE
```

2017-07-28 04:03:38 -07:00

providers

Merge pull request #49318 from dims/bail-on-block-storage-api-detection

2017-07-28 04:03:38 -07:00

BUILD

run hack/update-all

2017-06-22 11:31:03 -07:00

cloud.go

run hack/update-all

2017-06-22 11:31:03 -07:00

doc.go

…

OWNERS

remove some people from OWNERS so they don't get reviews anymore

2017-07-13 10:02:21 -07:00

plugins.go

add external cloudprovider to clerly denote the offloading off cloudprovider tasks

2017-03-06 10:45:13 -08:00

README.md

Update docs/ URLs to point to proper locations

2017-06-05 22:13:54 -07:00

README.md

Deprecation Notice: This directory has entered maintenance mode and will not be accepting new providers. Cloud Providers in this directory will continue to be actively developed or maintained and supported at their current level of support as a longer-term solution evolves.

Overview:

The mechanism for supporting cloud providers is currently in transition: the original method of implementing cloud provider-specific functionality within the main kubernetes tree (here) is no longer advised; however, the proposed solution is still in development.

Guidance for potential cloud providers:

Support for cloud providers is currently in a state of flux. Background information on motivation and the proposal for improving is in the github proposal.
In support of this plan, a new cloud-controller-manager binary was added in 1.6. This was the first of several steps (see the proposal for more information).
Attempts to contribute new cloud providers or (to a lesser extent) persistent volumes to the core repo will likely meet with some pushback from reviewers/approvers.
It is understood that this is an unfortunate situation in which 'the old way is no longer supported but the new way is not ready yet', but the initial path is unsustainable, and contributors are encouraged to participate in the implementation of the proposed long-term solution, as there is risk that PRs for new cloud providers here will not be approved.
Though the fully productized support envisioned in the proposal is still 2 - 3 releases out, the foundational work is underway, and a motivated cloud provider could accomplish the work in a forward-looking way. Contributors are encouraged to assist with the implementation of the design outlined in the proposal.

Some additional context on status / direction:

1.6 added a new cloud-controller-manager binary that may be used for testing the new out-of-core cloudprovider flow.
Setting cloud-provider=external allows for creation of a separate controller-manager binary
1.7 adds extensible admission control, further enabling topology customization.