bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
9.04k stars 9.22k forks source link

Not able to add image Pull secrets for single user docker image #30575

Open cvatsops opened 6 hours ago

cvatsops commented 6 hours ago

Name and Version

bitnami/jupyterhub 8.0.1

What architecture are you using?

None

What steps will reproduce the bug?

I have deployed jupyterhub using below command:

helm install my-release oci://registry-1.docker.io/bitnamicharts/jupyterhub

I want to use a custom image for singleUser for which i also need to add pull secrets for it.

I have added that for this parameter: Singleuser deployment parameters

But after upgrading the helm chart , image puller pod is failing with 403 Forbidden. Please help where also in the chart do i need to update the value

Are you using any custom parameters or values?

Yes , i have added imagepull secret for singleUser:

Singleuser deployment parameters

NOTE: The values in this section are used for generating the hub.configuration value. In case you provide

a custom hub.configuration or a configmap, these will be ignored.

@param singleuser.image.registry [default: REGISTRY_NAME] Single User image registry

@param singleuser.image.repository [default: REPOSITORY_NAME/jupyter-base-notebook] Single User image repository

@skip singleuser.image.tag Single User image tag (immutabe tags are recommended)

@param singleuser.image.digest Single User image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag

@param singleuser.image.pullPolicy Single User image pull policy

@param singleuser.image.pullSecrets Single User image pull secrets

singleuser: image: registry: my_registry_name repository: my_repo_name tag: v1 digest: ""

Specify a imagePullPolicy

## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images
##
##
pullPolicy: Always
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
## e.g:
## pullSecrets:
##   - my_secret_name
##
pullSecrets:
  - my_secret_name

What is the expected behavior?

SingleUser pod should be created with my custom image with it's valid pull secrets.

What do you see instead?

imagePuller pod not getting spawned up due to forbidden error. So please suggest how to resolve this.

Additional information

No response