Skip to content

Documentation conflict for automatic creation of pull secrets #2730

@hekimazuri

Description

@hekimazuri

What happened?
Using the information detailed in https://www.devspace.sh/docs/configuration/images/pull (6.x, latest) that say to use the field createPullSecrets to disable automatic creation of pull secrets, pull secrets are still created.
The 5.x docs https://www.devspace.sh/docs/5.x/configuration/images/pull-secrets say to use the field createPullSecret, which does disable automatic creation of pull secrets.

What did you expect to happen instead?
Documentation that indicates createPullSecrets should be updated to the working createPullSecret.

How can we reproduce the bug? (as minimally and precisely as possible)
Setting the plural setting createPullSecrets to false when running a build will still create pull secrets. Using the singular version will prevent creation.

My devspace.yaml:

version: ...
...

Local Environment:

  • DevSpace Version: 6.3.2
  • ARCH of the OS: AMD64
    Kubernetes Cluster:
  • Cloud Provider: google
  • Kubernetes Version: v1.25.11-gke.1700

Anything else we need to know?

This can easily lead to leaked credentials of a user that believes they've taken measures to prevent their creds from being uploaded to a remote server.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions