You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/cluster-administration/cloud-providers.md
+2-71Lines changed: 2 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ weight: 30
6
6
7
7
<!-- overview -->
8
8
This page explains how to manage Kubernetes running on a specific
9
-
cloud provider.
9
+
cloud provider. There are many other third-party cloud provider projects, but this list is specific to projects embedded within, or relied upon by Kubernetes itself.
10
10
11
11
<!-- body -->
12
12
### kubeadm
@@ -116,15 +116,6 @@ If you wish to use the external cloud provider, its repository is [kubernetes/cl
116
116
The Azure cloud provider uses the hostname of the node (as determined by the kubelet or overridden with `--hostname-override`) as the name of the Kubernetes Node object.
117
117
Note that the Kubernetes Node name must match the Azure VM name.
118
118
119
-
## CloudStack
120
-
121
-
If you wish to use the external cloud provider, its repository is [apache/cloudstack-kubernetes-provider](https://github.com/apache/cloudstack-kubernetes-provider)
122
-
123
-
### Node Name
124
-
125
-
The CloudStack cloud provider uses the hostname of the node (as determined by the kubelet or overridden with `--hostname-override`) as the name of the Kubernetes Node object.
126
-
Note that the Kubernetes Node name must match the CloudStack VM name.
127
-
128
119
## GCE
129
120
130
121
If you wish to use the external cloud provider, its repository is [kubernetes/cloud-provider-gcp](https://github.com/kubernetes/cloud-provider-gcp#readme)
@@ -138,11 +129,6 @@ Note that the first segment of the Kubernetes Node name must match the GCE insta
138
129
139
130
If you wish to use the external cloud provider, its repository is [kubernetes-sigs/cloud-provider-huaweicloud](https://github.com/kubernetes-sigs/cloud-provider-huaweicloud).
140
131
141
-
### Node Name
142
-
143
-
The HUAWEI CLOUD provider needs the private IP address of the node as the name of the Kubernetes Node object.
144
-
Please make sure indicating `--hostname-override=<node private IP>` when starting kubelet on the node.
145
-
146
132
## OpenStack
147
133
This section describes all the possible configurations which can
148
134
be used when using OpenStack with Kubernetes.
@@ -362,19 +348,7 @@ Kubernetes network plugin and should appear in the `[Route]` section of the
The OVirt cloud provider uses the hostname of the node (as determined by the kubelet or overridden with `--hostname-override`) as the name of the Kubernetes Node object.
370
-
Note that the Kubernetes Node name must match the VM FQDN (reported by OVirt under `<vm><guest_info><fqdn>...</fqdn></guest_info></vm>`)
371
-
372
-
## Photon
373
-
374
-
### Node Name
375
-
376
-
The Photon cloud provider uses the hostname of the node (as determined by the kubelet or overridden with `--hostname-override`) as the name of the Kubernetes Node object.
377
-
Note that the Kubernetes Node name must match the Photon VM name (or if `overrideIP` is set to true in the `--cloud-config`, the Kubernetes Node name must match the Photon VM IP address).
@@ -388,46 +362,3 @@ If you are running vSphere < 6.7U3, the in-tree vSphere cloud provider is recomm
388
362
{{< /tabs >}}
389
363
390
364
For in-depth documentation on the vSphere cloud provider, visit the [vSphere cloud provider docs site](https://cloud-provider-vsphere.sigs.k8s.io).
391
-
392
-
## IBM Cloud Kubernetes Service
393
-
394
-
### Compute nodes
395
-
By using the IBM Cloud Kubernetes Service provider, you can create clusters with a mixture of virtual and physical (bare metal) nodes in a single zone or across multiple zones in a region. For more information, see [Planning your cluster and worker node setup](https://cloud.ibm.com/docs/containers?topic=containers-planning_worker_nodes).
396
-
397
-
The name of the Kubernetes Node object is the private IP address of the IBM Cloud Kubernetes Service worker node instance.
398
-
399
-
### Networking
400
-
The IBM Cloud Kubernetes Service provider provides VLANs for quality network performance and network isolation for nodes. You can set up custom firewalls and Calico network policies to add an extra layer of security for your cluster, or connect your cluster to your on-prem data center via VPN. For more information, see [Planning your cluster network setup](https://cloud.ibm.com/docs/containers?topic=containers-plan_clusters).
401
-
402
-
To expose apps to the public or within the cluster, you can leverage NodePort, LoadBalancer, or Ingress services. You can also customize the Ingress application load balancer with annotations. For more information, see [Choosing an app exposure service](https://cloud.ibm.com/docs/containers?topic=containers-cs_network_planning#cs_network_planning).
403
-
404
-
### Storage
405
-
The IBM Cloud Kubernetes Service provider leverages Kubernetes-native persistent volumes to enable users to mount file, block, and cloud object storage to their apps. You can also use database-as-a-service and third-party add-ons for persistent storage of your data. For more information, see [Planning highly available persistent storage](https://cloud.ibm.com/docs/containers?topic=containers-storage_planning#storage_planning).
406
-
407
-
## Baidu Cloud Container Engine
408
-
409
-
### Node Name
410
-
411
-
The Baidu cloud provider uses the private IP address of the node (as determined by the kubelet or overridden with `--hostname-override`) as the name of the Kubernetes Node object.
412
-
Note that the Kubernetes Node name must match the Baidu VM private IP.
413
-
414
-
## Tencent Kubernetes Engine
415
-
416
-
If you wish to use the external cloud provider, its repository is [TencentCloud/tencentcloud-cloud-controller-manager](https://github.com/TencentCloud/tencentcloud-cloud-controller-manager).
417
-
418
-
### Node Name
419
-
420
-
The Tencent cloud provider uses the hostname of the node (as determined by the kubelet or overridden with `--hostname-override`) as the name of the Kubernetes Node object.
421
-
Note that the Kubernetes Node name must match the Tencent VM private IP.
422
-
423
-
## Alibaba Cloud Kubernetes
424
-
425
-
If you wish to use the external cloud provider, its repository is [kubernetes/cloud-provider-alibaba-cloud](https://github.com/kubernetes/cloud-provider-alibaba-cloud).
426
-
427
-
### Node Name
428
-
429
-
Alibaba Cloud does not require the format of node name, but the kubelet needs to add `--provider-id=${REGION_ID}.${INSTANCE_ID}`. The parameter `${REGION_ID}` represents the region id of the Kubernetes and `${INSTANCE_ID}` denotes the Alibaba ECS (Elastic Compute Service) ID.
430
-
431
-
### Load Balancers
432
-
433
-
You can setup external load balancers to use specific features in Alibaba Cloud by configuring the [annotations](https://www.alibabacloud.com/help/en/doc-detail/86531.htm) .
0 commit comments