kubermatic / kubermatic/dashboard
OpenStack Load Balancer Classes: allow CRUD operations after UC creation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 73
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 31
Description
Not sure whether this also requires additional work in the backend, if so, an additional issue might be required there.
What would you like to be added? / User Story:
Thanks to #7646 (related to kubermatic/kubermatic#14918 and https://github.com/kubermatic/kubermatic#14305 and maybe others), load balancer classes can be created during UC creation.
But what do I do if I made a mistake? What, if I made changes on OpenStack I need to reflect? What if I need a class that I didn't think necessary during cluster creation?
It should be possible to CRUD load balancer classes post-creation the same as it can be done during cluster creation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how load balancer classes are created during UC creation, using #7646 and its linked context as entry points. Determine whether dashboard and backend changes are needed; done means users can create, read, update, and delete these classes after UC creation with the same capability available during creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100