kubermatic
Enablement of cloud drive for OpenStack in KKP UI
Place the enablement checkboxes to:
- Admin panel: Edit Datacenter menu
- Create Cluster, 4th step when MDs are created
We also need an option to enforce/enable config drive at the data center level. Once enforced, the user shouldn't be able to modify this value from the dashboard.
Do take into account https://github.com/kubermatic/kubermatic/issues/13618 and specially https://github.com/kubermatic/kubermatic/issues/13618#issuecomment-2304573588, before starting the implementation.
https://github.com/kubermatic/kubermatic/pull/13603 is needed for this
@archups: The label(s) /label /backport-needed cannot be applied. These labels are supported: blocked by backend, merge-type/merge, merge-type/rebase, needs details, service accounts, Epic, MVP, customer-request, design, feature, proposal, ready-to-challenge, redesign, sig/api, sig/app-management, sig/cluster-management, sig/community, sig/infra, sig/networking, sig/ui, sig/virtualization, sprint, team/marketing, team/ps, lifecycle/frozen, backport-needed, backport-complete, ee, needs-release-testing, test/require-vsphere, test/require-kubevirt, test/require-vmwareclouddirector, test/require-nutanix. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?
In response to this:
/label /backport-needed
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
KKP backend provides support for this https://github.com/kubermatic/kubermatic/issues/13618 since KKP release 2.26. Backport is needed because enable config drive feature is not working as expected just with the KKP backend change. Also worth taking note of https://github.com/kubermatic/kubermatic/pull/13656#issuecomment-2331242885 Thanks!