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
Docker UCP closely integrates into Microsoft Azure for its Kubernetes Networking
8
-
and Persistent Storage feature set. UCP deploys the Calico CNI provider, in Azure
8
+
and Persistent Storage feature set. UCP deploys the Calico CNI provider. In Azure
9
9
the Calico CNI leverages the Azure networking infrastructure for data path
10
10
networking and the Azure IPAM for IP address management. There are
11
11
infrastructure prerequisites that are required prior to UCP installation for the
@@ -20,24 +20,23 @@ IP addresses.
20
20
21
21
You have two options for provisoning IPs for the Kubernetes cluster on Azure:
22
22
- Docker UCP provides an automated mechanism to configure and maintain IP pools
23
-
for stand-alone Azure VMs. This service runs within the calico-node daemonset
23
+
for standalone Azure VMs. This service runs within the calico-node daemonset
24
24
and by default will provision 128 IP address for each node. This value can be
25
-
configured via the `azure_ip_count`in the UCP
25
+
configured through the `azure_ip_count`in the UCP
26
26
[configuration file](../configure/ucp-configuration-file) before or after the
27
-
UCP installation. Note that if this value is reduced postinstallation, existing
28
-
VMs will not be reconciled, and the user will have to manually edit the IP count
27
+
UCP installation. Note that if this value is reduced post-installation, existing
28
+
VMs will not be reconciled, and you will have to manually edit the IP count
29
29
in Azure.
30
30
- Manually provision additional IP address for each Azure VM. This could be done
31
-
as part of an Azure Virtual Machine Scale Set via an ARM template, an example
32
-
can be found [here](#set-up-ip-configurations-on-an-azure-virtual-machine-scale-set).
33
-
Note the `azure_ip_count` value in the UCP
31
+
as part of an Azure Virtual Machine Scale Set through an ARM template. You can find an example [here](#set-up-ip-configurations-on-an-azure-virtual-machine-scale-set).
32
+
Note that the `azure_ip_count` value in the UCP
34
33
[configuration file](../configure/ucp-configuration-file) will need to be set
35
-
to 0. If not UCP's IP Allocator service will provision IP Address on top of
34
+
to 0, otherwise UCP's IP Allocator service will provision the IP Address on top of
36
35
those you have already provisioned.
37
36
38
37
## Azure Prerequisites
39
38
40
-
The following list of infrastructure prerequisites need to be met in order
39
+
You must meet these infrastructure prerequisites in order
41
40
to successfully deploy Docker UCP on Azure.
42
41
43
42
- All UCP Nodes (Managers and Workers) need to be deployed into the same
@@ -58,7 +57,7 @@ Group hosting the UCP Nodes. Note, if using a separate networking Resource
58
57
Group the same Service Principal will need `Network Contributor` access to this
59
58
Resource Group.
60
59
61
-
The following information will be required for the installation:
60
+
UCP requires the following information for the installation:
62
61
63
62
-`subscriptionId` - The Azure Subscription ID in which the UCP
64
63
objects are being deployed.
@@ -69,9 +68,8 @@ objects are being deployed.
69
68
70
69
### Azure Configuration File
71
70
72
-
For Docker UCP to integrate in to Microsoft Azure, an Azure configuration file
73
-
will need to be placed within each UCP node in your cluster. This file
74
-
will need to be placed at `/etc/kubernetes/azure.json`.
71
+
For Docker UCP to integrate into Microsoft Azure, you need to place an Azure configuration file
72
+
within each UCP node in your cluster, at `/etc/kubernetes/azure.json`.
75
73
76
74
See the template below. Note entries that do not contain `****` should not be
0 commit comments