Page last updated:

This topic provides an overview of the components and resources needed to install PCF in airgapped environments, including the typical corresponding automation resources.

Offline Components

To run PCF offline, you must obtain resources from the internet and move them into offline components that store and use them. The method you use to move a resource from Pivotal Network or GitHub into an offline environment can vary from setting up a designated proxy to burning a DVD.

The following image displays types of resources and the components you must move them to in your offline environment. It also includes a jumpbox. The jumpbox is a Linux host for running commands such as bosh, uaac, and fly. You could use the Ops Manager VM for this purpose.

Offline components

The following table provides more detail about resources and the component you must move them to:

Resource Component
Pivotal Network products such as tiles, stemcells, BOSH releases, and Ops Manager S3 and artifact store
Pipelines and scripts Git
Configuration Git
Container images Docker Registry, S3, or artifact store
Third Party Resources such as NSX-T and OSS BOSH releases Artifact store
Backup artifacts S3

Architectural Patterns

The following sections describe three architectural patterns for running PCF in air-gapped environments. The pattern you use depends on how your environment is set up.

5a02014d… Fixes issue #610 [#168442660]

Pattern One: Artifact Store with Internet Access

It is common for organizations to deploy an artifact store such as Artifactory or Nexus as a gateway to the Internet. In this configuration, the artifact store is typically configured as a Docker mirror.

This pattern includes an S3 component that is used only for backups of the PCF installation.

Internet artifact store

The following table provides an example of how you might handle resources in this scenario:

Resource Component
Pivotal Network products such as tiles, stemcells, BOSH releases, and Ops Manager This architectural pattern presents the challenge of getting Pivotal Network resources from the Internet into the artifact store. For example, Artifactory and Nexus cannot interact directly with Pivotal Network. You could place Pivotal Network resources in an artifact store either through a remote Concourse worker with access to the Internet, by downloading them from the Internet and placing them in the artifact store manually, or some other method.
Pipelines and scripts Store in Git. Use manual clone and push. Modify pipelines to use registry_mirror.
Configuration Store in Git. Use manual clone and push.
Container images Store in the artifact store that you configured as a mirror.
Third Party Resources such as NSX-T and OSS BOSH releases Store in a generic artifact store repository.
Backup artifacts Store in a S3 blobstore.

Pattern Two: Completely Offline

In completely offline environments, you must bring in all resources manually and store them in the available local components.

Completely offline

In this architectural pattern, you must configure pipelines to watch components for changes and apply updates when available. The following table provides an example of how you might handle resources in this scenario:

Resource Component
Pivotal Network products such as tiles, stemcells, BOSH releases, and Ops Manager Manually upload to Nexus.
Pipelines and scripts Modify pipelines to use a local Harbor Docker registry. Manually clone an online environment, bring it to the offline environment on DVD, and push it to offline Git.
Configuration Store in your offline Git.
Container Images Get from the Internet, transfer to USB, and push to offline Harbor.
Third Party Resources such as NSX-T and OSS BOSH releases Store in a generic artifact store repository.
Backup artifacts Store in a S3 blobstore.

Pattern Three: TLS Intercepting Proxy

This pattern allows Internet access, but only through a proxy that decrypts and rewrites TLS certificates. In general, this resembles an online install, however it requires that you add your corporate certificate to all BOSH-deployed VMs.

Tls intercepting proxy

Some of the challenges in this pattern include the following:

  • Any automation that calls to the Internet will fail if it does not have the corporate certificate in its trust store.
  • Concourse tasks that do not use resources do not receive updated BOSH root certificates. This means you must configure tasks to ignore TLS errors or update the root certificates as part of the tasks.