Skip to main content
Version: 6.x (Latest)

Pull Secrets

DevSpace allows you to configure additional pull secrets that should be created in the target namespace. For each configured pull secret in the devspace.yaml, DevSpace will create a secret in the target namespace and add the secret to the imagePullSecrets field of the service account.

For images, DevSpace will also automatically create a pull secret, if authentication data can be found in the local docker store and creation is enabled via createPullSecret.

Image Pull Secrets are defined in the pullSecrets section of the devspace.yaml.

# If you don't want to specify the password and username directly in the config
# you can use variables, .env file or save the credentials in the local docker store
pullSecrets:
my-pullsecret:
registry: my-registry.com:5000
username: ${REGISTRY_USER}
password: ${REGISTRY_PASSWORD}

Configuration

pullSecrets required <pullSecret_name>:object

PullSecrets are image pull secrets that will be created by devspace in the target namespace during devspace dev or devspace deploy. DevSpace will merge all defined pull secrets into a single one or the one specified.

<pullSecret_name> required string

Name is the pull secret name to deploy

registry required string

The registry to create the image pull secret for. Empty string == docker hub e.g. gcr.io

username required string

The username of the registry. If this is empty, devspace will try to receive the auth data from the local docker

password required string

The password to use for the registry. If this is empty, devspace will try to receive the auth data from the local docker

email required string

The optional email to use

secret required string

The secret to create

serviceAccounts required string[]

The service account to add the secret to