cloud-provider job from kubo/0.11.1
Github source:
8bd23ae
or
master branch
Properties¶
cloud-provider
¶
gce
¶
network-name
¶Google Cloud network name. Required when cloud-provider.type is gce
project-id
¶Google Cloud project id. Required when cloud-provider.type is gce
service_key
¶Google Cloud service key that is used by cloud-provider.
worker-node-tag
¶Google Cloud tag that identifies only worker nodes in this deployment.
openstack
¶
auth-url
¶The URL of the keystone API used to authenticate.
ca-file
¶CA file to connect to your OpenStack cluster (Optional).
- Default
""
domain-id
¶Used to specify the id of the domain your user belongs to (Optional).
- Default
""
domain-name
¶Used to specify the name of the domain your user belongs to (Optional).
- Default
""
password
¶Refers to the password of a valid user set in keystone.
region
¶Used to specify the identifier of the region to use when running on a multi-region OpenStack cloud (Optional).
- Default
""
tenant-id
¶Used to specify the id of the project where you want to create your resources.
tenant-name
¶Used to specify the name of the project where you want to create your resources (Optional).
- Default
""
trust-id
¶Used to specify the identifier of the trust to use for authorization (Optional).
- Default
""
username
¶Refers to the username of a valid user set in keystone.
type
¶Type of Cloud Provider to use
- Example
gce, vsphere
vsphere
¶
datacenter
¶Datacenter to be used
datastore
¶Datastore to use for provisioning volumes using storage classes/dynamic provisioning
insecure-flag
¶set to 1 if the host above uses a self-signed cert
- Default
0
password
¶Password for vCenter
port
¶Default 443 for vCenter
- Default
443
scsicontrollertype
¶vSphere vSCSI adapter type name
- Default
pvscsi
server
¶IP/URL for vCenter
user
¶User name for vCenter
vm-uuid
¶VM Instance UUID of virtual machine which can be retrieved from instanceUuid property in VmConfigInfo, or also set as vc.uuid in VMX file. If empty, will be retrieved from sysfs (requires root)
working-dir
¶Folder in which VMs are provisioned
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/cloud-provider/
directory
(learn more).
bin/cloud-provider_utils
(frombin/cloud-provider_utils.erb
)config/cloud-provider.ini
(fromconfig/cloud-provider.ini.erb
)config/service_key.json
(fromconfig/service_key.json.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.