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
Post-deployment
If you initially encounter any errors while accessing content on your new server for the first time, your first resolution step should be to cause a rebuild of the content item. The technique involved to cause a rebuild differs depending on the type of content and can range from a simple page reload to a toolbar button available from within the Posit Connect dashboard interface.
Optimizing access for existing content (if any)
If your Posit Connect installation is new, you can skip to the next step.
As long as your new Posit Connect server continues to use the same database and is mounted to the same NFS location, all of the source-level content bundles previously deployed to your old server will be available to the new server. However, to properly present the content, the new server will need to restore the runtime environment required by the content (referred to as rebuilding the content). Rebuilding is performed automatically upon the first-time access of a piece of content, but when this happens, users can experience a less-than-optimal performance (as dependent packages are downloaded and installed).
While this normally OK, it is recommended that important content be rebuilt ahead of first-user access. Posit Connect provides tooling which allows an admin or publisher to initiate the rebuild without requiring user direct access to the content.
Using the list of content that you prepared during the Identification of performance critical and important content step, you can use the rsconnect content build tool to rebuild the content.
It is a good practice to validate access to the content you have rebuilt.
Custom content container image preparation
Most organizations choose to exercise control over the docker images used for content execution rather than simply using the public images which Posit makes available.
If this applicable to your installation, see the Content Image Appendix for more information.
Implement High Availability
With the Helm Chart values.yaml file created earlier, the deployment of Posit Connect was configured with 1 replica so that traffic for a single connection is always routed to the same Posit Connect pod.
To implement multiple replicas of the Posit Connect pod, you will need to first update the replica count within your values.yaml file and then run helm upgrade. For example, the following change would enable three replicas to be running:
# Controls how many instances of Posit Connect will be created.
replicas: 3When enabling High Availability for Posit Connect, it is required that an Ingress Controller be configured with “Sticky Sessions” enabled. This configuration is described in the Enabling External Access appendix.