the check-override-allowed component did not know how to deal with the k8s
version question because of its tri state and how we deal with the patch version
that is an override but not really an override. I added a check to verify the
mode is view and we have the param then display param so we don't initialize the
form-version component which has logic to inject the current version into its
versions dropdown but only if we're new, editing, or cloning.
rancher/rancher#23478rancher/rancher#23465
Refactor and decouple launch cluster
adds new routes for selecting cluster, selecting cluter template, and launching
cluster
Add first version of cluster template selection logic
WIP - First version of cluter-template resource pages & components
cluster template index
adds cru-cluster-template
save cluster template and cluster template revision
refactor rke cluster driver and add rke cluster driver to clust temp
add cluster template revision page
template revision changes
more questions
refactor cluster networking into component
cluster template questions components
first itteration of working add question
fixups for ct and ctr's
general fixes
quick revision select on new revision page
Move name, expose ctr name, move ctr source
Refactor ct/ctr table to use grouped form
share member added
single template no revisions rows
translations
translation changes
css toggle
css toggle on all elements
inline override
initial apply cluster template
initial show or lock when applying a cluster template
validation bug
first run at windows support overrides
abstract check override with component that yields
add check for override to most sections
bulk remove cluster template revision
more check override
handle errors better for ctrs
translations
bugs
add toggle to azure cloud provider
auth endpoint fix
computed override check and refactor
fixup question override inputs
remove cluster launch route
review fixups
cluster edit
fixup alias properties for overrides
Cody Jackson
Westly Wright