This makes the node group upgrade ux closer to the ux of AWS console.
Removes the node group version select, replaces with a radio.
Adds logic to set the new nodegroup version on edit to the version of other nodegroups
Adds logic to prevent node group version upgrade when cluster version is being upgraded.
rancher/rancher#28965rancher/rancher#28966rancher/rancher#28968
- The entire tag collection needs to be sent if it changed
- I noticed that when editing a tag key each letter was added so I resolved that as well
rancher/rancher#28949
adds both tooltip warning on cluster row and alert warning on cluster dashboard
version can only be updated on edit when cluster version is different from node group version
all other times we set the node group version to the clusters version
rancher/rancher#28335
error handler
wip - dev for aws cloud creds
wip - refactor aws login
wip - kms key
wip - encrypt secrets
wip - private access & vpcs
wip - translations and formatting
wip - more cleanup
remove unneeded code
wip - node groups
add ability to disable value label
fix double import, fix double negative disable add button and expose
addbuttonenabled
clean up public access and node groups
cleanup variable names and default config
eks regions
wip - eks v2 select
differentiate v1/2 amazon eks providers
clean up node groups, translations
unionize top errors
Consolidate aws util statics
WIP - Import/Cloud Creds
tweak cloud cred events for eks driver
WIP new import selector
drop unneeded variables eks import
kms keys cleanup
allow user to enter if the kms keys call fails
firefox styles
drop vpc selection and group subnets by vpcs
import cluster name input if allClusters fails to load from eks
make eks import a bit more dynamic
fix bug in driver eks for default subnet
more imported cleanup
eks v2 edit
eks v2 vendors
remove use cloud creds temp branchs
push current version to version choices if it doesnt exist
eks v2 rename cloudcred param
fix eks v2 versions
clean up for pr
This now checks to see if there's and RKE template.
If there is an RKE template and the scheduleScanned is disabled
the button will be disabled unless there's an override available for
the scheduledClusterScan.enabled field.
rancher/rancher#26150
- Added a Snapshot Now button to the top of the table
- Added a Restore Snapshot option to the actions of each row which will
select the current row when opening the modal
rancher/rancher#25511
The profile helper methods were attached to the cluster model.
Unfortunately, the cluster isn't available when creating a new rke
template.
To resolve this I moved all of the cis helpers out of the cluster model
and utils and moved them into a cisHelpers service so they could be
used without access to the cluster itself.
- Added Set Alert button
- This will set the appropriate options for cis
- Added Set Schedule button
- This will scroll the settings into view
- Added a modal so profiles can be picked
This refactoring removed code duplication and
provides a more cohesive experience across all
of the pages that you can run a scan.
This will also now check and ensure the following
- there aren't running ClusterScans
- this isn't a windows cluster
- systemProject is available
- the cluster is active
- the action link is available
When the above isn't the case Run CIS Scan will not be present in
the cluster action drop downs and the Run CIS Scan but
will be disabled on the CIS Scans and CIS Scan Detail
pages.
rancher/rancher#24759rancher/rancher#25298
Run CIS Scan was broken on the cluster list page because
currentCluster was being used instead of just using the current cluster.
I also removed the redirect and just use a growl notification to
indicate the scan is running.
rancher/rancher#25241rancher/rancher#25159
Improving the UX of CIS based on the feedback that was received during
the review.
- Sort scans by date so newest will be on top.
- Details should be sorted by state in Fail, Skipped, Pass order
- Add a Run CIS Scan action to the cluster menu.
The cluster upgrade notification wasn't properly updating when
the user enabled and disabled a revision. It required that the
page was refreshed before display the fresh data.
This resolves this issue by watching more appropriate keys
int he relevant computed properties. The most relevant
being the revision.@each.enabled on the latestRevision property.
rancher/rancher#23126
- We will only conditionally render template/revision section on the
monitoring page if the cluster is using a template. This was
crashing the page before.
- We will now make sure there's a string when invoking replace
when generating the template and revision display names.
- We will now respect the enable flag of template revisions
when determining if an upgrade is available.
rancher/rancher#23126
We want to make it easier for someone that is managing multiple
clusters to see what template and template revision a cluster
is using. We also want to make it easy for a user to notice
that a cluster isn't using the latest revision.
To achieve this we added the template and revision to a column
in the clusters table to display both. We also indicate add
a warning badge beside a revision when the revision isn't
the latest.
rancher/rancher#22047
Westly Wright
Cody Jackson
Vincent Fiduccia
loganhz
jesse.millan
loganhz
n313893254