Skip to content

Conversation

@89luca89
Copy link
Contributor

/kind bugfix

resolves #2603
Closes ENG-1154

Fixed an issue where DevSpace would attempt to create the namespace for localregistry even it the namespace indeed exists.
This came out as a problem in the moment the user wasn't authorized to create namespaces, thus checking before leaping now.

@netlify
Copy link

netlify bot commented Mar 21, 2023

Deploy Preview for devspace-docs canceled.

Built without sensitive environment variables

Name Link
🔨 Latest commit 32cfa90
🔍 Latest deploy log https://app.netlify.com/sites/devspace-docs/deploys/6419adb256156400087b8258

Signed-off-by: Luca Di Maio <luca.dimaio1@gmail.com>
Copy link
Collaborator

@lizardruss lizardruss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May be able to simplify with a different API call, but I could be missing context.

Signed-off-by: Luca Di Maio <luca.dimaio1@gmail.com>
Copy link
Collaborator

@lizardruss lizardruss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@lizardruss lizardruss merged commit 0a4bb60 into devspace-sh:main Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Running local image registry should not require permission to patch "namespaces" resource if the namespace already exists

2 participants