* added ui instructions for cluster list to access-clusters
* re-org access-clusters so that 'Cluster List' becomes a searchable heading
* rewording
* added instructions and links for Global Settings
* added global config + retitle/rephrase
retitle to disambiguate global settings from global config
listed some relevant global config items that need more info
* correction: updated access-clusters page in /docs, not /versioned_docs
* added Nodes UI instructions
* download kubeconfig UI instructions added/modified
one file contained correct instructions but they were somewhat convoluted, as you can download the file from a page mentioned earlier in the suggested instructions and the button thery describe is an icon, not labeled with any text
* restoring formatting
* updated pathway for image list downloads
* finding rancher-images.txt
* added instructions for Apps Marketplace
* link pointing to v1 monitoring
* link pointing to v1 dashboards
* added links for v1 notifiers, logging tools
* global dns entries, global dns providers, catalog links added
* Rancher portal > Rancher UI
* updated access-clusters page
* rm note & add third way to access cluster dashboard
* heading levels
* addressed comments in global-configuration
* addressed comments for nodes-and-node-pools
* addressed comment on authorized-cluster-endpoint
* rm'd create apps steps
* updated kubeconfig download instructions
* adjusting headers
* updated images list instructions as version # is now an About link
* restored intro to monitoring-and-alerting
* KubeConfig > kubeconfig (except for naming the UI label)
* left navigation sidebar > left navigation
* Update docs/how-to-guides/new-user-guides/manage-clusters/access-clusters/authorized-cluster-endpoint.md
Co-authored-by: Billy Tat <btat@suse.com>
* applied changes to v2.7 docs
---------
Co-authored-by: Billy Tat <btat@suse.com>
While testing a build, I noticed that the self-assment guide redirects weren't resolving from pages-for-subheaders/rancher-hardening-guides.md. I updated the links on that page to point to the current name for those pages. When I tested the links in docusaurus.config, it seemed like the redirects were formatted correctly and pointed to the right paths. I know we had a similar issue some months ago with other redirects. Updating the links on pages-for-subheaders/rancher-hardening-guides.md is a quick fix -- we still need to look into why the redirects weren't resolving.
Although we don't have confirmation that this applies to earlier versions of Rancher (2.6 and below) I'm merging as the information is important for the latest (2.7). Specifically, it's not clear to me from the AWS site if you can install earlier versions.
* Update upgrades.md
Add consideration for the current 'Rancher Setup' AWS Marketplace offering, which uses the deployment name of 'rancher-setup'.
* Apply suggestions from code review
* versioned docs sync to 2.7
---------
Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
Co-authored-by: martyav <marty.avedon@suse.com>
