0.7.3

  • Bump Connect version to 2024.06.0

Changelog

0.7.2

  • Bump Connect version to 2024.05.0
  • BREAKING: local execution only
    • Default installed R versions upgraded to 4.4.0 and 4.3.3.
    • Default installed Python versions upgraded to 3.12.1 and 3.11.7.
  • Enable TensorFlow by default in values.yaml when running in local or off-host execution mode.

0.7.1

  • Add documentation about PostgreSQL database configuration and mounting passwords from secrets as env variables

0.7.0

  • BREAKING: the prometheus endpoint has changed from port 9108 to 3232 by default
    • We are now using an internal prometheus endpoint with all new metrics
    • As a result, the graphiteExporter sidecar has been removed
    • Some metrics from the graphiteExporter will no longer be present
    • The parent / main “off-switch” for prometheus is at prometheus.enabled
    • To revert to the old exporter, set prometheus.legacy=true (and please reach out to let us know why!)

0.6.7

  • Documentation site updates

0.6.6

  • Bump Connect version to 2024.04.1

0.6.5

  • Bump Connect version to 2024.04.0

0.6.4

  • Update the default content images in default-runtime.yaml and default-runtime-pro.yaml to include newer R, Python and Quarto versions.
  • Enable Python and Quarto by default in values.yaml when running in local or off-host execution mode.

0.6.3

  • Bump Chronicle Agent to version 2024.03.0

0.6.2

  • Bump Connect version to 2024.03.0

0.6.1

  • Updates to support standalone documentation site

0.6.0

  • BREAKING: The generated service will now have type ClusterIP set by default.
  • Add support for setting the loadBalancerIP or clusterIP.
  • Ignore nodePort settings when the service is not a NodePort.
  • Improve the documentation for some service-related settings.

0.5.14

  • Bump Connect version to 2024.02.0

0.5.13

  • Add option to set pod.terminationGracePeriodSeconds

0.5.12

  • Bump Connect version to 2024.01.0

0.5.11

  • Bump Connect version to 2023.12.0

0.5.10

  • Add licensing section to the README to provide guidance on using a license file, license key or license server.

0.5.9

  • Bump Connect version to 2023.10.0

0.5.8

  • Bump rstudio-library to 0.1.27
    • Fix an issue with mountPath and subPath when license.file.mountSubPath is true

0.5.7

  • Add support for setting tolerations for Connect

0.5.6

  • Bump Connect version to 2023.09.0

0.5.5

  • Add support for sharedStorage.subPath

0.5.4

  • Bump Connect version to 2023.07.0

0.5.3

  • Added ability to assign labels in service accounts.

0.5.2

  • Add support for pod.command and pod.env for Connect off-host execution sessions
    • pod.command is a hack for now… it will be removed eventually

0.5.1

  • Bump Connect version to 2023.06.0

0.5.0

  • BREAKING: Change default OS / OS prefix to ubuntu2204-. Bionic support is EOL as of 2023-04-30 This change also impacts the default set of content execution images. Changing the execution environment OS will cause a rebuild for all currently deployed content.
    • If you want to revert this change, set image.tagPrefix=bionic- (server), launcher.defaultInitContainer.tagPrefix=bionic- (content-init), and modify the set of content images defined by launcher.customRuntimeYaml to use bionic instead of ubuntu2204
    • BREAKING: Off-Host Execution Beta users who are currently evaluating this feature set can use the example values defined in https://github.com/rstudio/helm/tree/main/examples/connect/beta-migration to assit with the content migration from bionic to jammy
  • Trim the default set of content execution images to the 4 latest releases of Python/R.
    • A Quarto installation has been added to all content-base images.
  • Allow launcher to configure the Kubernetes API URL and the Service Account token from inside the pod instead of specifying on prestart via environment variables.
  • Update documentation and README for a bit more clarity.
  • Add podDisruptionBudget values
  • Add topologySpreadConstraints values

0.4.2

  • Add a metrics port to the service, which ensures that the ServiceMonitor actually works

0.4.1

  • Fix issue in templates that prevented numeric service accounts from being used.

0.4.0

  • BREAKING: change pod.nodeSelector to nodeSelector for consistency with other charts and the community. In order to highlight the change, we error if pod.nodeSelector is anything other than empty.
  • BREAKING: turn pod.serviceAccountName WARNING into an error as well.
  • Add provisional support for launcher.templateValues.pod.env, launcher.templateValues.pod.nodeSelector, and launcher.templateValues.pod.priorityClassName
  • NOTE: we are making these values induce failure so that CI systems and other deployments are explicit about the unused values. Please share feedback if this creates problems in your environment.

0.3.19

  • Update documentation to remove “beta” label and explain production recommendations

0.3.18

  • Bump Connect version to 2023.03.0

0.3.17

  • Bump Connect version to 2023.01.1

0.3.16

  • Bump rstudio-library to 0.1.24
    • Update RBAC definition to support listing of service accounts

0.3.15

  • Bump Connect Launcher templates to 2.3.0-v1
    • added app.kubernetes.io/managed-by: "launcher" in both job.tpl and service.tpl
    • resource requests and limits calculations in job.tpl
    • sets serviceAccountName in job.tpl for content jobs
    • launcher.templateValues.pod.serviceAccountName to set the default service account for content pods

0.3.14

  • Bump Connect version to 2023.01.0

0.3.13

  • add launcher.defaultInitContainer.securityContext to configure the securityContext on the default initContainer (##319)
  • add serviceMonitor section for defining a ServiceMonitor object [(##126)[https://github.com/rstudio/helm/issues/126]]
  • improve consistency in the prometheusExporter configuration section (as compared to the rstudio-workbench chart)

0.3.12

  • Bump Connect version to 2022.12.0

0.3.11

  • Add sharedStorage.volumeName for PVCs that reference a PV
  • Add sharedStorage.selector as well

0.3.10

  • Deprecate pod.serviceAccountName in favor of rbac.serviceAccount.name (##267)
  • Allow un-setting rbac.serviceAccount.name (##294)

0.3.9

  • Fix a typo in launcher.defaultInitContainer.imagePullPolicy (##289)

0.3.8

  • Add updated templates for launcher.templateValues and session container customization
    • Add customization of securityContext and containerSecurityContext (##293)
    • Fix typo in serviceAccountName implementation (##251)
    • Add affinity and tolerations (##271 and ##283)
  • Add an image.tagPrefix value to make customizing the operating system easier
  • Add a launcher.defaultInitContainer.tagPrefix value to make customizing the operating system easier

0.3.7

  • Bump Connect version to 2022.11.0

0.3.6

  • Bump Connect version to 2022.10.0

0.3.5

  • Fix appVersion to target bionic-2022.09.0, to reflect new image naming conventions that include the operating system.

0.3.4

  • Bump Connect version to 2022.09.0

0.3.3

  • Add a check to provide faster feedback if launcher.enabed=true without setting up shared storage

0.3.2

  • Bump Connect version to 2022.08.1

0.3.1

  • Bump Connect version to 2022.08.0

0.3.0

  • BETA BREAKING: We moved launcher.contentInitContainer customizations to launcher.defaultInitContainer
    • This should only affect if you are using launcher.enabled=true, which is still in Beta
    • Values are treated the same, so a simple modification to the key should resolve any issues
  • RStudio Connect with off-host execution is now in Public Beta
  • Add support for the launcher.useTemplates value
    • This enables greater customization of session creation as well as better labels and annotations out of the box
    • To make use of the default session templates, configure values in launcher.sessionTemplate
  • Enable logging using RStudio Connect’s new logging configuration (effective with version 2022.07)
  • Add a toggle for launcher.defaultInitContainer.enabled to turn off the default init container
    • When using the launcher, it is important that sessions have the RStudio Connect “session runtime” available
    • By default, we make these available through an init container, but they can also be provided other ways
    • By disabling this setting, you are opting into managing this runtime requirement yourself
  • Add values for pod.port and service.targetPort
  • Allow launcher.additionalRuntimeImages and launcher.customRuntimeYaml="pro" (##238, ##92)

0.2.38

  • Bump rstudio-library chart version
  • Relax RBAC for pod/logs to remove write-related privileges

0.2.37

  • Bump Connect version to 2022.06.2

0.2.36

  • Bump Connect version to 2022.06.0

0.2.35

  • Add the ability to set annotations to the Persistent Volume Claim.

0.2.34

  • Make resources configuration backwards compatible with the previous enabled flag (##218)

0.2.33

  • Add sharedStorage.mountContent value configuration option. When this setting is enabled, the chart will configure Connect’s Launcher.DataDirPVCName to use the PVC defined by sharedStorage.name. If this setting is used, then config.Launcher.DataDir must not be set.

0.2.32

  • Update rstudio-library chart version. Add support for lists in INI file sections.

0.2.31

  • Bump Connect version to 2022.05.0

0.2.30

  • Simplify resources configuration and allow resources configuration on the sidecar container
    • Worth noting that if baseline enabled, defaults have changed to not specify resources. Prototype recommendations remain in the chart values as a comment

0.2.29

  • Add pod.securityContext value configuration option

0.2.28

  • Bump Connect version to 2022.04.2

0.2.27

  • Bump Connect version to 2022.04.1

0.2.26

  • Fix ingress definition issues with older Kubernetes clusters (##139)

0.2.25

  • Bump Connect version to 2022.03.2

0.2.24

  • Bump Connect version to 2022.03.1

0.2.23

  • Bump Connect version to 2022.02.3

0.2.22

  • Bump Connect version to 2022.02.2

0.2.21

  • Bump Connect version to 2022.02.0

0.2.20

  • Add pod.affinity value to define affinity for the pod

0.2.19

  • Update rstudio-library chart version. This adds support for extraObjects
  • Add extraObjects value. This allows deploying additional resources (with templating) straight from the values file!

0.2.18

  • Bump Connect version to 2021.12.1

0.2.17

  • Make startupProbe, readinessProbe and livenessProbe more configurable (##97)
    • They still use the enabled key to turn on or off
    • We then remove this key with omit, and pass the values verbatim to the template (as YAML)

0.2.16

  • Update rstudio-library chart version. This adds a helper for rendering Ingress resources
  • Create k8s.networking.io/v1 Ingress resource when ingress.enabled: true and Kubernetes version is >=1.19 (##117)

0.2.15

  • Bump Connect version to 2021.12.0

0.2.14

  • Bump library-chart version

0.2.13

  • Add configuration values for pod.haste to set (or unset) the RSTUDIO_CONNECT_HASTE variable
  • Add a pod.labels values option (##101)

0.2.12

  • Bump Connect version to 2021.11.1

0.2.11

  • move “privileged: true” into values.yaml, because it is no longer necessary for rstudio-connect server or sessions when launcher is enabled.
    • To disable when using the launcher, set securityContext: null
    • NOTE: securityContext: {} will not remove the default, because helm values merge objects by default
  • location for RStudio Connect’s KubernetesProfilesConfig file has changed from /etc/rstudio/launcher.kubernetes.profiles.conf to /etc/rstudio-connect/launcher/launcher.kubernetes.profiles.conf so as to not conflict with RStudio Workbench

0.2.10

  • Update default RStudio Connect version to 2021.11.0

0.2.9

  • Add imagePullSecrets value option (##57)

0.2.8

  • Bump rstudio-library chart version

0.2.7

  • Update default RStudio Connect version to 2021.10.0

0.2.6

  • Update rstudio-library chart version

0.2.5

  • Update default RStudio Connect version to 2021.09.0

0.2.4

  • Enabled Python support in Connect by default when launcher.enabled=true
  • Any values defined in the config section now take precendence over those that are set by the Helm chart’s logic.

0.2.3

  • Update default RStudio Connect version to 2021.08.2

0.2.2

  • Added a new parameter rbac.clusterRoleCreate to values.yaml to allow for disabling the creation of the ClusterRole that allows for access to the nodes API. This API is used to ensure that all of the IP addresses for nodes are available when reporting the addresses of the node that is running a particular job so that clients can connect to it. This is generally not a needed permission for the Launcher as the internal IP is usually sufficient, so it is disabled by default.

0.2.1

  • Update docs

0.2.0

  • BREAKING: Licensing configuration now uses a license section. For example, license: my-key should be changed to

    license:
  key: my-key

  • Added support for floating licenses and license files.

  • Default RStudio Connect version is now 1.9.0.1

  • Add a prestart.bash script for use when launcher.enabled=true

    • when launcher.enabled=true, the chart changes command and args dynamically to use this script
    • if you set command and args yourself, we will use your settings instead. Be sure:
      • that /scripts/prestart.bash is executed (for Kubernetes setup)
      • that /usr/local/bin/startup.sh is executed (for licensing)

  • Add RBAC via the rstudio-library chart

  • Add runtime.yaml configuration (for runtime containers)

  • Change default configuration when launcher is enabled

  • Add the ability to more easily customize launcher.kubernetes.profiles.conf

    • Set up the profiles defaults to include the init container

  • Allow more easily mounting a named PVC that was not created by the chart

  • Make the “target” launcher namespace configurable

  • Add a default value for service.port: 80

0.1.2

  • Add ingress as an option
  • Add annotations to deployment so that the pods roll when config changes

0.1.1

  • Update to 1.8.6.2
  • Update docs

0.1.0

  • Change naming convention
    • This fixes issues with namespacing
    • However, it will damage backwards compatibility, particularly for PVCs if using sharedStorage.create = true
    • If you need to migrate data, set replicas: 0, upgrade, and then copy the data to the new PVC
    • Alternatively, you can set fullnameOverride: "previous-release-name" to force backwards compatibility
      • Finally, deployment selectors have changed, so you will need to delete the current deployment manually, then put back with helm upgrade --install
    • Use helm diff upgrade to ensure things are working as you expect before upgrading

0.0.3

  • Add HA, Postgres, PVC, monitoring

0.0.2

  • Minimally viable