📖 Roll out tools with latest NGINX proxy image to all users

[michaeljcollinsuk]

User Story

As a AP engineer
I need all our users to be using the latest NGINX proxy image
So that we avoid more users hitting "502 Bad Gateway" error when accessing tools

Value / Purpose

The new NGINX proxy image resolves the 502 error users are increasingly reporting

Useful Contacts

No response

User Types

No response

Hypothesis

No response

Proposal

We need to create a release for each version of our tools that uses version 1.1.0 of Analytical Platform Cloud Development Environment NGINX Proxy.

We currently have users using multiple versions of each Rstudio and JupyterLab, so we will need to create new release for each actively used version. VS Code releases already uses the CDE Nginx Proxy, so no new releases are required.

For RStudio versions I propose we create new releases for the following:

Rstudio version	RStudio image tag	High memory?
4.1.2	4.1.2-9	Yes
4.2.3	4.2.3	No
4.4.1	4.4.1-1	No

Each of the above releases should use chart version 5.0.0. The values section of the release need to be updated to remove overriding the proxy image tag, as the chart is set to use the new version.

There will be other versions of RStudio that are being used, which we may need to update or push users to one of the above release - @Gary-H9 is working on a script to get details of which versions of tools users have deployed currently.

Jupyter releases TBC

Additional Information

No response

Definition of Done

• RStudio releases created in Control Panel
• Jupyter releases created in Control Panel
• Comms sent out via support channel instructing users to update
• Incident updated to resolved in PagerDuty

[michaeljcollinsuk]

There is an issue with Jupyter releases, discussion in this thread https://mojdt.slack.com/archives/C06NFN4FMNG/p1731511062509669

[michaeljcollinsuk]

We have decided to hold off on making the new releases available generally to all users, until there is a method/plan to deprecate the previous releases. Otherwise there is a risk that we will find ourselves in a state where we double the number of releases available with users split across both releases. We are also in the process of creating a new formalised release process, so once this is completed we can follow this process for the new versions.

If users report encountering the 502 error in the meantime, we can add them to the restricted releases that have been created. For VS code, we should always encourage users to use the latest version as this uses the latest NGINX proxy image. For reference, see support request where I asked a user to upgrade https://github.com/ministryofjustice/data-platform-support/issues/954#issuecomment-2476917949

[michaeljcollinsuk]

I have added a sub-task to this issue - allow releases to be deprecated.

[michaeljcollinsuk]

Some extra details about the existing RStudio releases:

4.4.1

• RStudio server 2024.09.0 "Cranberry Hibiscus"
• R 4.4.1

4.4.0

• RStudio server 2024.04.0 "Chocolate Cosmos"
• R 4.4.0

4.2.3

• RStudio server 2023.03.0 "Cherry Blossom"
• R 4.2.3

4.1.2

• RStudio server 2022.02.0 "Prairie Trillium"
• R 4.1.2

[michaeljcollinsuk]

Added an example to the draft release comms doc https://docs.google.com/document/d/16z3c9AwO31Zbj--ozeO_QlfbL5SVK2bw6qY3d6dpSz8/edit?pli=1&tab=t.2sjtpa47ryun

[michaeljcollinsuk]

Release have been added and "Unrestricted". We have also updated users via the support channel and PagerDuty, see our tracking issue related to the 502 errors for further context

[michaeljcollinsuk]

In addition to new CDE NGINX releases, I have marked all older releases as "deprecated" and added a message instructing users to update