kubermatic / kubermatic/dashboard
machine deployments should be editable when usercluster apiserver is reachable
- Dominant language
- Go
- Stars
- 50
- Forks
- 73
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 31
Description
### What happened
Current state is that when one component of kkp usercluster pods isn't in rtunning state machine deployments are not editable and not visible even when it is, for example, a rolling restart of etcd pods. Machine deployments should be visible and editable when the usercluster is reachable.
customer ref: 9172
### Expected behavior
### How to reproduce
### Environment
- UI Version: v2.30
- API Version: v2.30
- Domain:
- Others:
### Current workaround
### Affected user persona
kkp users
### Business goal to be improved
### Metric to be improved
Contributor guide
Research direction
Start by tracing the dashboard logic that controls machine deployment visibility and editing when a usercluster component is not running, using the issue's rolling-restart scenario as the first case. Verify the behavior when the usercluster API server is reachable and confirm that machine deployments are both visible and editable in that state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100