Aster v1.0.1
·
15 commits
to main
since this release
What's new
Kubeconfig conflict detection & resolution
- Aster now detects when several configured kubeconfig sources define the same context or cluster name with different content, and marks the affected context in the picker with a one-line warning (hover shows which server wins and from which file).
- Clicking the warning opens a dialog listing each colliding entry with a Rename in file action: the colliding entry is renamed inside the source kubeconfig file, in-file references are updated (contexts pointing at a renamed cluster, current-context), and the original is preserved once as
<file>.aster.bak.
Review dry-runs as a diff
- Mutation dry-runs (scale, edit, delete, create) are now reviewed as a GitHub-style unified diff with word-level highlights instead of a plain YAML preview.
- Server-managed fields (
generation,resourceVersion) are filtered out of the review so only real changes show. - Applying a mutation now presents the resourceVersion the dry-run ran against, avoiding conflicts against stale list snapshots.
Fixes
- Selecting a context in the picker restores that context's namespace instead of clearing the filter.