Skip to content

Gateway: cannot change my kube config and check connection again #23558

@adietish

Description

@adietish

Is your enhancement related to a problem? Please describe

When in the connection wizard, any changes to my kubeconfig are not taken into account. I have to start all over again.

Steps:

  1. ASSERT: have an expired token in kube config
  2. EXEC: in gateway: click "Connect to Dev Spaces" and click "Check connection and Continue"
  3. ASSERT: connecting fails "Unauthorized" (expired token)
Image
  1. EXEC: correct the token in your kube config and (back in gateway) click "Check connection and Continue" again

Result:
Connecting still fails. The changes that I made to the kube config are not taken into account.

Workaround:
Start all over again.

Describe the solution you'd like

I would like the connection wizard to take my updated token into account, I dont want to have to start all over again.

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

Labels

area/editorsarea/gatewaykind/enhancementA feature request - must adhere to the feature request template.severity/P1Has a major impact to usage or development of the system.

Projects

Status

🚧 In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions