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.

Appendix: Release Notes

RStudio Connect >= 2022.07.0

  • Starting with RStudio Connect 2022.07.0, the release notes for Launcher/Kubernetes related features have moved to the main Connect release notes.

Documentation

  • We have updated the bitnami/postgresql and kvaps/nfs-server-provisioner charts to use pinned verisons for better reproducibility.

RStudio Connect 2022.06.0

New

  • Administrators may now configure job-expiry-hours for the job launcher using the Launcher.KubernetesJobExpiryHours setting. (#21567)

  • Administrators may now use ClusterIP services instead of NodePort services when launching content jobs on Kubernetes. To enable this feature, set the value of the spec.type field to be ClusterIP in Launcher’s service.tpl template configuration file. (#21597)

Fixed

  • Fixed an issue in Connect that sometimes occurs when the job launcher silently disconnects from pod output streams without sending an EOF to Connect. This lead to jobs showing up as “running” indefinitely in Connect. (#21499)

Breaking

  • Connect will now fail to start when Launcher.DataDir contains a : character. If you were using this setting previously to mount an NFS share to content pods, we recommend migrating to the new Launcher.DataDirPVCName instead. See the external storage appendix for details. (#21488)

RStudio Connect 2022.05.0

New

  • Publishers may now select an image for content execution when using off-host execution by specifying the environment.image field in the manifest.json. (#21379)

  • Administrators may now use a Kuberenetes PVC to mount Launcher’s DataDir to content Pods by specifying Launcher.DataDirPVCName. RStudio Connect will mount the PVC using subPaths to maintain isolation between content items. (#19392)

  • RStudio Connect will now recognize and respond to certain error events from Kubernetes. Currently, only ImagePullBackoff is detected. When a Pod enters the ImagePullBackoff state, RStudio Connect will terminate the Job and return an error back to the user. (#20306)

Fixed

  • Interactive content Pods should now receive SIGINT signals from the Launcher by default and shut down gracefully. This should prevent interactive Pods from going to the ERROR state and allow them to be cleaned up properly. (#20895)