Describe the bug
After editing a Kubernetes object through Headlamp's built-in editor (tested with Ingress objects), clicking "Save & Apply", being redirected back to the list view, and receiving the success confirmation message, re-opening the same object for editing still shows the old version of the manifest — not the version that was just saved.
The editor only loads the updated manifest after manually refreshing the page or navigating away to another section and back.
This can lead to confusion and accidental reverts, as a user may believe they are editing the latest version of the object when they are actually looking at a stale manifest.
Expected behavior:
After a successful "Save & Apply", the in-memory representation of the object should be updated with the applied changes once the success confirmation is received. This way, re-opening the editor immediately shows the current version of the manifest without requiring a page refresh or navigation away and back.
To Reproduce
- Go to the Ingresses list view (or any other resource list) in Headlamp.
- Click on the three-dot menu on the right side of the object you want to edit.
- Click "Edit" to open the YAML editor.
- Make a change to the manifest (e.g., add an annotation).
- Click "Save & Apply".
- Get redirected back to the list view.
- After a few seconds, a success confirmation toast appears at the bottom-left of the screen (the operation appears to be async).
- Click on the same Ingress again and open the editor.
- See that the manifest shown is the old version, without the change just applied.
- Navigate away to another section and back, or refresh the page.
- Open the editor again — now the updated manifest is shown correctly.
Environment (please provide info about your environment):
- Installation type: Helm (in-cluster)
- Headlamp Version: 0.40.1
- Browsers tested: Brave (Chromium-based), Safari
- Access: via ingress-nginx
Are you able to fix this issue?
No.
Additional Context
Tested with Ingress objects, but the issue likely affects other resource types as well since the editor and caching mechanism appear to be shared across resource kinds.
This may be related to the object not being re-fetched or the local cache/store not being invalidated after a successful edit operation.
Describe the bug
After editing a Kubernetes object through Headlamp's built-in editor (tested with Ingress objects), clicking "Save & Apply", being redirected back to the list view, and receiving the success confirmation message, re-opening the same object for editing still shows the old version of the manifest — not the version that was just saved.
The editor only loads the updated manifest after manually refreshing the page or navigating away to another section and back.
This can lead to confusion and accidental reverts, as a user may believe they are editing the latest version of the object when they are actually looking at a stale manifest.
Expected behavior:
After a successful "Save & Apply", the in-memory representation of the object should be updated with the applied changes once the success confirmation is received. This way, re-opening the editor immediately shows the current version of the manifest without requiring a page refresh or navigation away and back.
To Reproduce
Environment (please provide info about your environment):
Are you able to fix this issue?
No.
Additional Context
Tested with Ingress objects, but the issue likely affects other resource types as well since the editor and caching mechanism appear to be shared across resource kinds.
This may be related to the object not being re-fetched or the local cache/store not being invalidated after a successful edit operation.