Skip to content

Improve topology debugging UX and release tag consistency#68

Merged
kaskol10 merged 2 commits into
mainfrom
feat/views-extension
Apr 22, 2026
Merged

Improve topology debugging UX and release tag consistency#68
kaskol10 merged 2 commits into
mainfrom
feat/views-extension

Conversation

@kaskol10

@kaskol10 kaskol10 commented Apr 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • extend topology UX with compact/full pod list toggle, hide-daemonset toggle, node drill-in, daemonset-only mode, node-local search, and per-node persisted drill-in filters
  • add CPU and memory request values to drill-in pod rows for faster debugging context
  • fix local docker-compose defaults by mapping frontend to 3000:80 and mounting host kubeconfig into API container
  • update release automation to bump both backend and frontend Helm image tags in values.yaml whenever chart version is bumped

Test plan

  • cd frontend && npm run lint
  • cd frontend && npm run build
  • manual topology UI sanity checks (overview toggles, drill-down controls, filter persistence)
  • validate compose config changes (docker-compose.yml) for local API/UI wiring

Notes

  • Helm release workflow now updates charts/karpenter-optimizer/values.yaml tag fields so backend/frontend image tags stay aligned with chart version.

Add richer topology drill-down controls (daemonset-only mode, per-node search, persistent node-level filters, and per-pod CPU/memory request values), add compatibility behavior for older topology APIs, and fix docker-compose defaults for frontend port mapping plus kubeconfig mounting.

Made-with: Cursor
Update release automation to keep backend and frontend image tags in values.yaml aligned with each chart version, preventing mismatched deployments after chart updates.

Made-with: Cursor
@kaskol10 kaskol10 merged commit 93ce33c into main Apr 22, 2026
6 checks passed
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.

1 participant