Break CruResource cancel footer logic into component
Refactor apps/install to remove CruResource, use new footer component
Add Yaml Preview to Chart Install
When working on adding the yaml preview to the chart install page i came
to the conclusion that the footer piece is all that is required out of
CruResource for that page. Chart install requires a different set of
actions on yaml save so rather than try to kluge action handeling in it
makes more sense to decouple the common elements, ie the footer and confirm cancel
- Increased alert text size by 2px
- Hide alerts if there aren't any
- Switched from created to age
- Adjusted event column widths
- Fixed a tooltip position bug
rancher/dashboard#925
- This will allow us to get the appropriate singular/plural for the labels
- Updates Total Resources to reflect the new spacing that was added
rancher/dashboard#887
- Replaced naked strings with translations
- Removed the suffix prop and just use name since both are the same for each of our cases.
rancher/dashboard#885
We only show the live metrics for worker nodes. The HA cluster that I created on GKE doesn't add the 'node-role.kubernetes.io/...' label. The
lack of this label causes us to filter out all nodes since we don't
consider them to be workers.
rancher/dashboard#776
If a user edited a resource and then attempted to create a new
resource they would be taken to the view page of the previously
edited resource.
This was being caused by adding the existing route params to the
location used by the create button. More specifically the existing
params contained an id which caused the mode to be computed
incorrectly.
By removing all of the existing params the create, createAsYaml, edit, editAsYaml, clone and view pages all appear to work.
rancher/dashboard#758