This site is archived

Posit Connect support for off-host content execution has entered General Availability (GA).
Documentation about off-host execution is now included in the Connect Admin Guide.
The instructions presented here were associated with the off-host execution beta and are now obsolete.

Configuration and Deployment

Using Kubernetes to host Posit Connect service and content execution

Planning and Analysis

There are several planning and analysis steps which should be performed ahead of the deployment sequence:

  • Analysis of existing content requirements (for migrations)
  • Identification of performance critical content (for migrations)
  • Network connectivity verification
  • Network storage capacity verification
  • Posit Connect license validation (for migrations)
  • Planning for downtime (for migrations)

Analysis of existing content requirements

Note

If your Posit Connect installation is new, you can skip to the next step.

Posit Connect uses images to prepare and execute your content. These images must satisfy the existing R & Python content requirements as well as any system dependencies required for the content’s dependent packages or libraries.

The Server API Cookbook contains the recipe Content Runtimes - R and Python versions in use which will assist you in understanding the needs of your existing content.

Note

Posit has made a set of public docker images available, which are used by the Helm Chart by default. We recommend that you perform your initial migration using these default images and then after confirming the default images are functional, proceed to configuring your custom images.

Identification of performance critical and important content

Note

If your Posit Connect installation is new, you can skip to the next step.

Following the post-deployment validation of the new Posit Connect server, you will have the opportunity to optimize first-time access of content previously deployed to your old server. In addition, it is important to identify critical content items which should be included within the initial validation of your new Posit Connect server.

To support this step, you will need to understand your organization’s internal needs and assemble a list of content GUIDs and access paths that should be targeted.

For those organizations which are unable to easily identify mission-critical content items, the rsconnect content search tool included in the rsconnect-python Python package can be used to perform usage analysis. This tool provides content query functionality which can be invoked to satisfy your organization’s objectives in this area.

Pull the helm charts used in this guide

# Posit Connect
helm repo add rstudio https://helm.rstudio.com

# Postgres (optional)
helm repo add bitnami https://charts.bitnami.com/bitnami

# NFS (optional)
helm repo add kvaps https://kvaps.github.io/charts

# Pull the latest versions of the helm charts
helm repo update

Network connectivity verification

Note

If you don’t have PostgreSQL or NFS installations yet, don’t worry. We will create them in the next section.

  1. Verify that the Kubernetes Cluster has connectivity to NFS. If migrating, also confirm connectivity to the NFS path where the Posit Connect data files are located.
  2. Verify that you can access the PostgreSQL server from within the cluster.
  3. Verify that the ports required for accessing the Posit Connect server are not blocked (by default, 30000 - 32767 is the range expected).

Network storage capacity verification

Make sure you have enough space on the NFS server. If you have an existing installation, we recommend you allocate two times the amount of space currently being used.

Posit Connect license validation

If you plan to use an existing Posit Connect license, confirm that you have enough license activations available by reaching out to your Posit Customer Success representative before proceeding. To request a separate evaluation license, you can also email Customer Success or sales@posit.co and specify that you are trialing this feature.

Planning for downtime

Note

If your Posit Connect installation is new, you can skip to the next step.

Coordinate with your stakeholders; your Posit Connect server will be out-of-service during the migration.

The time required will depend on the following factors:

  • Number of content bundles published to your server
  • The difference of GID / UID assignments between your existing files vs what is present on the runtime images
  • The amount of content migration optimization that you choose to perform