Expected behavior and actual behavior:
Expected: creating or updating any resource (users, projects, repositories, artifacts, registries) should be immediately reflected in the web portal.
Actual: the web portal shows stale content indefinitely. New robot users, repositories, registries, and artifacts do not appear, and updates to existing items are not shown. The API returns the correct, up-to-date data when queried directly — only the portal UI is affected. Confirmed not a browser-cache issue: tested with hard refresh, cache clearing, DevTools "disable cache", and multiple browsers, with no change.
Steps to reproduce the problem:
- Create a new resource via the portal (e.g. a robot account) — see attached recording.
- Observe the resource is created successfully (confirm via API).
- Return to the relevant portal page (with or without a refresh).
- New resource is not shown. Same behaviour occurs for edits to existing resources.
Versions:
- harbor version: 2.15.0 across all pods.
- docker engine version: 29.6.2, build dfc4efb
- docker-compose version: 5.3.1 via
docker baseline
Additional context:
- Deployment: Kubernetes (not docker-compose), Harbor with Notary disabled.
- Nginx used for reverse proxying, running on the host outside the Kubernetes cluster.
- Cloudflare in front, handling TLS/DNS.
- Screen recording demonstrating the issue attached: https://github.com/user-attachments/assets/0072a3de-6cd5-476e-8dbf-17b9cca1e18c
- Harbor is ran via Kubernetes, there is no /var/log/harbor to be found. Alongside this, the logs show nothing of importance, simply just
GET / HTTP/1.1's; and no result in harbor-core.
Expected behavior and actual behavior:
Expected: creating or updating any resource (users, projects, repositories, artifacts, registries) should be immediately reflected in the web portal.
Actual: the web portal shows stale content indefinitely. New robot users, repositories, registries, and artifacts do not appear, and updates to existing items are not shown. The API returns the correct, up-to-date data when queried directly — only the portal UI is affected. Confirmed not a browser-cache issue: tested with hard refresh, cache clearing, DevTools "disable cache", and multiple browsers, with no change.
Steps to reproduce the problem:
Versions:
dockerbaselineAdditional context:
GET / HTTP/1.1's; and no result in harbor-core.