Bug: Error when creating the default pull secret
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 460
- Forks
- 756
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 88
Description
Description
Creating a default pull secret from a newly created Namespace fails.
The UI sends an invalid request while trying to add a value to the imagePullSecrets array. In this case, the target array does not exist yet, but the request attempts to add an item to it. As a result, the API rejects the request and the default pull secret is not created.
Steps to reproduce
- Open the console connected to a clean Kubernetes cluster.
- Go to Namespaces.
- Create a new Namespace.
- Open the newly created Namespace details page.
- Click the action to create a default pull secret.
- Enter a secret name.
- Click Save.
Actual result
The operation fails with the following error:
HttpError: the server rejected our request due to an error in our request
Expected result
The default pull secret should be created successfully and displayed on the Namespace page.
Additional details
This was reproduced on the main (49745c2) branch with "pure" k8s cluster.
https://github.com/user-attachments/assets/3a04035a-f6be-4d6e-a3eb-2548cd89bc26
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Namespace details page's action for creating a default pull secret and inspect how the request updates the imagePullSecrets array when the array is absent. Reproduce the steps on a clean Kubernetes cluster, then confirm the request succeeds and the created secret appears on the Namespace page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100