Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make creation of imported clusters use v3/management cluster instead of v1/provisioning #13151

Open
eva-vashkevich opened this issue Jan 17, 2025 · 2 comments
Assignees
Labels
area/clusterprovisioningv2 kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@eva-vashkevich
Copy link
Member

Is your feature request related to a problem? Please describe.
There is an inconsistency between POST operations for imported cluster. We want to make it more consistent and avoid adding non-provisioning fields or duplicating fields from the v3 cluster to the v1 cluster.

Describe the solution you'd like

We want to switch to using v3/management cluster for both POST operations (creation and edit, currently it is only used for edit).

@eva-vashkevich eva-vashkevich added this to the v2.11.0 milestone Jan 17, 2025
@eva-vashkevich eva-vashkevich self-assigned this Jan 17, 2025
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 17, 2025
@eva-vashkevich eva-vashkevich changed the title Make imported clusters creation and edit Make creation of imported clusters use v3/management cluster instead of v1/provisioning Jan 17, 2025
@richard-cox
Copy link
Member

This will hopefully be a short term step until the next phase of cluster management comes in.

It also aligns with how the cluster will be edited (port from ember v3/cluster to v1/mgmt cluster - #13064)

@richard-cox
Copy link
Member

Linking rancher/rancher#35192

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterprovisioningv2 kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

2 participants