-
Notifications
You must be signed in to change notification settings - Fork 33
Expand file tree
/
Copy path_service-networks-v3.html.md.erb
More file actions
16 lines (13 loc) · 998 Bytes
/
_service-networks-v3.html.md.erb
File metadata and controls
16 lines (13 loc) · 998 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
When you deploy PCF, you must create a statically defined network to host the component virtual
machines that constitute the PCF infrastructure.
PCF components, like the Cloud Controller and UAA, run on this infrastructure network.
On-demand PCF services may require that you host them on a network that runs separately
from the PCF default network. You can also deploy tiles on separate service networks to
meet your own security requirement.
PCF v2.1 and later include dynamic networking. Operators can use this dynamic networking with
asynchronous service provisioning to define dynamically-provisioned service networks. For more
information, see [Default Network and Service Network](#on-demand).
In PCF v2.1 and later, on-demand services are enabled by default on all networks. Operators can
create separate networks to host services in BOSH Director, but doing so is optional.
Operators select which network hosts on-demand service instances when they configure the tile for
that service.