This patch clears out all of the old provider code from this directory
to make room for the new, maintained tree that will be imported into
this project.
Depends-On: I38e2168e311536cc63932d906a46e1b1cf3ac4bf
Change-Id: I0d3b2c3805cc47edbb2aac14f757d5bdc114899a
* Don't try to install etcd. work with the one from devstack
* Remove taint so the node is schedulable
* Update list of failing tests
Change-Id: I2719fa2a3cadd57a62dfe9102b939edef2b36fd9
Need to disable all iptables rules for the moment till
we figure out which ones exactly to remove. Unless we
disable the iptables, we cannot run kubedns.
Change-Id: Ia42f5fc353791d3d417574785e5c006b603d050d
- Use v1.7.0-alpha.1 tag of the kubernetes master branch
- Add support for NFS scenarios
- Tweak list of tests
- Add ENABLE_HOSTPATH_PROVISIONER
- Allow specifying full job failure names
Change-Id: I0b4840858236de9f49c7797564ec5b6a8032875e
Seems to work somewhat. the pre/post/gate hook(s) are not kicking
in though. So just getting this in and will iterate.
Change-Id: Ibf6e7a431271de8fb8533e269bb4985fd3e74ff0
The cloudprovider is being refactored out of kubernetes core. This is being
done by moving all the cloud-specific calls from kube-apiserver, kubelet and
kube-controller-manager into a separately maintained binary(by vendors) called
cloud-controller-manager. The Kubelet relies on the cloudprovider to detect information
about the node that it is running on. Some of the cloudproviders worked by
querying local information to obtain this information. In the new world of things,
local information cannot be relied on, since cloud-controller-manager will not
run on every node. Only one active instance of it will be run in the cluster.
Today, all calls to the cloudprovider are based on the nodename. Nodenames are
unqiue within the kubernetes cluster, but generally not unique within the cloud.
This model of addressing nodes by nodename will not work in the future because
local services cannot be queried to uniquely identify a node in the cloud. Therefore,
I propose that we perform all cloudprovider calls based on ProviderID. This ID is
a unique identifier for identifying a node on an external database (such as
the instanceID in aws cloud).
Change-Id: Ie0c4b3f0456a02b9af2846c5842da18939c9a15e
Support for cinder v1/v2 api with the new gophercloud/gophercloud
library. API version is configurable and defaulting autodetection.
Change-Id: I83de02beb08f50c15f8faa8a3f070d67fd64de41
* Add mercurial/hg to bindep
* Use latest golang (1.8.x)
* Print additional go related environment information
Change-Id: I053873945a24ab0f592051423d2e307b3bdf299e
Automatic merge from submit-queue (batch tested with PRs 40932, 41896, 41815, 41309, 41628)
Add custom CA file to openstack cloud provider config
**What this PR does / why we need it**: Adds ability to specify custom CA bundle file to verify OpenStack endpoint against. Useful in tests and PoC deployments. Similar to what https://github.com/kubernetes/kubernetes/pull/35488 did for authentication.
**Which issue this PR fixes**: None
**Special notes for your reviewer**: Based on https://github.com/kubernetes/kubernetes/pull/35488 which added support for custom CA file for authentication.
**Release note**: