The ShinyProxy Operator for Kubernetes uses Redis (Sentinel) for storing user and app sessions. The manifests provided by the operator are based on the Redis Helm chart created by Bitnami. Therefore, these manifests are using the Redis Docker images provided by Bitnami. Bitnami will remove these images on 28th August 2025. Therefore, you’ll have to update your deployment in order to use a different image.
To make this as easy as possible, we have copied the images into the openanalytics/redis and openanalytics/redis-sentinel Docker Hub repositories. We’ve also updated the Kubernetes manifests to use these images, starting with version 2.2.2 of the ShinyProxy Operator.
FAQ
How do I update my deployment?
If you are using the Redis setup provided by the operator, you’ll have a kustomization.yaml file similar to:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
namespace: shinyproxy
resources:
- github.com/openanalytics/shinyproxy-operator/docs/deployment/bases/redis-sentinel?ref=v2.2.1
- github.com/openanalytics/shinyproxy-operator/docs/deployment/bases/namespaced?ref=v2.2.1
- github.com/openanalytics/shinyproxy-operator/docs/deployment/bases/shinyproxy?ref=v2.2.1
- resources/shinyproxy.namespace.yaml
- resources/shinyproxy.shinyproxy.yaml
patches:
- path: patches/redis.secret.yaml
In order to use the images from the new location, change this line:
- github.com/openanalytics/shinyproxy-operator/docs/deployment/bases/redis-sentinel?ref=v2.2.1
to
- github.com/openanalytics/shinyproxy-operator/docs/deployment/bases/redis-sentinel?ref=v2.2.2
You can change the other version numbers as well, but the release contains no other changes or updates.
Finally deploy your changes, the Redis daemonset will restart and use the new images.
What if I don’t update?
If you don’t update the location of the images, the Redis pods will continue to run. However, if the pods are restarted (e.g. because of node maintenance or autoscaler eviction), the pods will fail to pull the image and thus fail to start. This will eventually break your ShinyProxy setup.
What if I’m using an older version of the operator?
You can continue to run the older version of the operator, but you must update the location of the Redis images. The easiest way is to only update the version of the Redis manifests (see above), this will not update the operator.
Note that only the location of the image is changed, but the used image itself is identical, therefore it will work with any version of the ShinyProxy Operator.
I run the operator on a Docker host, do I have to update?
No, the update is only required when you are using Kubernetes.
I pushed the Redis images to my own registry, do I have to update?
No, the image itself hasn’t changed, only the location. If you mirrored the image to your own registry, everything will keep working.
I’m using a Redis service from my cloud provider, do I have to update?
No, when you use a service like AWS ElastiCache or Azure Cache for Redis, you don’t use the images from Bitnami and therefore no change is required.