Fileupload fails with 413 error

[radhupr]

Bug description

My requirement is to have Rstusio and jupyternotebook setup for our users in onpremise kubernetes. I have some internal requirements which includes kyverno policy compliance and SSO login setup (plus some more but for now I will stick to this basic needs)

I am using the chart 4.1.0 version and changed the user image as below in values.yaml

singleuser:
  image:
    name: glcr.b-data.ch/jupyterlab/r/tidyverse
    tag: "4.4.2"

I also have hub.config setup to use azureAD authentication.

I can launch notebook as well as Rstudio from this. But the issue now is that, when I'm uploading a file >500M, the UI gives the error as below(first it gives a warning that file is large then followed by error)

Is there a way to address this? Do you suggest use of any other image instead of tidyverse for this purpose?

How to reproduce

Helm chart installed:

- name: jupyterhub
    repo: https://hub.jupyter.org/helm-chart/
    version: 4.1.0
    releaseName: jupyterhub
    namespace: jupyterhub
    valuesFile: values.yaml
    kubeVersion: 1.30.2

with singleuser image:

image:
    name: glcr.b-data.ch/jupyterlab/r/tidyverse
    tag: "4.4.2"

Upload a file from UI which is greater than 500M

Expected behaviour

File uploaded without any issue

Actual behaviour

Jupyternotebook behavior:

followed by

Rstudio error

Your personal set up

[manics]

Check your logs, it could be due to your singleuser server, your ingress, loadbalancer, etc. If you need more help please post on https://discourse.jupyter.org/ and share your logs along with your full configuration. Thanks!

[github-actions]

Hi there @radhupr 👋!

I closed this issue because it was labelled as a support question.

Please help us organize discussion by posting this on the https://discourse.jupyter.org/ forum. If it's your first time posting
please read https://discourse.jupyter.org/t/getting-good-answers-to-your-questions/1825.
The more information you provide the more likely we can help you.

Our goal is to sustain a positive experience for both users and developers. We use GitHub issues for specific discussions related to changing a repository's content, and let the forum be where we can more generally help and inspire each other.

Thanks you for being an active member of our community! ❤️